Hello all,
I recently tried using the alpha build of wxPython Phoenix and found
two serious bugs:
If you try to create a MultiChoiceDialog, Python fatally
crashes.
Also, if you add an item to a menu with the id wx.ID_EXIT,
Python fatally crashes.
I am running Windows XP SP3 and Python 3.3.3.
(The first bug is of special importance to me, because until it
is fixed, I will not be able to switch to using Python 3.)
Thank you.
– Timothy Johnson
Both issues runs fine for me with the demo. See attached pic.
Phoenix is still in development. And when running python 3 is buggier than with Python 2 as there are syntax differences that still need worked/ironed out.
If you are using the phoenix lib from robins github page with the PY3 fixes from my fork(library-branch), then you may or may not have better success.
Else you will just have to wait until more gets done.
Note you will have to merge these changes from the repo into your own wx dir manually.
Crude way of getting it to work: Basically if you drop the wx dir from robins github page over your build first, then do the same from the llibrary-branch from mine with the PY3 Fixes.
Else: use all the logs and Winmerge the smaller differences from robins after a certain point in the repo logs.
Please be patient. Robin will get to it when he gets more time for phoenix and wraps up the classic 3 build.
Happy Holidays.
On Monday, December 23, 2013 4:42:29 PM UTC-6, Johnsons in DE wrote:
Hello all,
I recently tried using the alpha build of wxPython Phoenix and foundtwo serious bugs:
If you try to create a MultiChoiceDialog, Python fatallycrashes.
Also, if you add an item to a menu with the id wx.ID_EXIT,Python fatally crashes.
I am running Windows XP SP3 and Python 3.3.3.
(The first bug is of special importance to me, because until itis fixed, I will not be able to switch to using Python 3.)
Thank you.
– Timothy Johnson
Metallicow,
Thank you for your reply.
Could you please provide a link to the GitHub page you are talking
about? I saw from the screenshot you attached that you are using
wxPython Phoenix r74528, but I can’t find any place to download that
version from.
Currently, I'm using r75338 from [http://wxpython.org/Phoenix/snapshot-builds/](http://wxpython.org/Phoenix/snapshot-builds/) . I had previously tried
downloading r75135 from there, but it had the same problems. The two
most recent downloads available on that page use wxWidgets 3.0.0, I
believe, but they are just the source, and I’d rather not have to
compile wxPython myself.
Thank you.
– Timothy Johnson
On Tuesday, December 24, 2013 7:03:07 AM UTC-5, Metallicow wrote:
On Monday, December 23, 2013 4:42:29 PM UTC-6, Johnsons in DE wrote:
Hello all,
I recently tried using the alpha build of wxPython Phoenix and foundtwo serious bugs:
If you try to create a MultiChoiceDialog, Python fatallycrashes.
Also, if you add an item to a menu with the id wx.ID_EXIT,Python fatally crashes.
I am running Windows XP SP3 and Python 3.3.3.
(The first bug is of special importance to me, because until itis fixed, I will not be able to switch to using Python 3.)
Thank you.
– Timothy Johnson
Both issues runs fine for me with the demo. See attached pic.
Phoenix is still in development. And when running python 3 is buggier than with Python 2 as there are syntax differences that still need worked/ironed out.If you are using the phoenix lib from robins github page with the PY3 fixes from my fork(library-branch), then you may or may not have better success.
Else you will just have to wait until more gets done.Note you will have to merge these changes from the repo into your own wx dir manually.
Crude way of getting it to work: Basically if you drop the wx dir from robins github page over your build first, then do the same from the llibrary-branch from mine with the PY3 Fixes.
Else: use all the logs and Winmerge the smaller differences from robins after a certain point in the repo logs.Please be patient. Robin will get to it when he gets more time for phoenix and wraps up the classic 3 build.
Happy Holidays.
Ok, seems you found the snapshots alright download the snapshot for your OS.
Then download robins Repo Here GitHub - RobinD42/Phoenix: wxPython's Project Phoenix. A new implementation of wxPython, better, stronger, faster than he was before.
Then Download My Fork’s “library-branch” https://github.com/Metallicow/Phoenix/tree/library-branch, there is also one etc fix if you need that for stc also btw.
I also have the wipz “WIPz Demo branch” here https://github.com/Metallicow/Phoenix/tree/demo
As I said this will be CRUDE way, but Drop your snapshot in first, then drop the wx dir from robins repo in second overwriting. Third drop the wx dir from my fork in. Forth, and the etg if you need that stc fix.
If all your PythonPaths are set up and your wx.pth is right at this point you can then place the demo dir from my demo branch wherever you want and it will/should fire up.
If you have trouble restarting the demo again(Ex: second time), you may have to delete StcCodePageSettings.ini as it is a portable item now and is still wipz.
Note: that anything robin fixed after whenever I forked the repo in his repo are fixed needing winmerged in.
Consider patching/posting any other PY3 bugs you find if this all works for you on wxPython-dev,
Again Happy Holidays.
On Tuesday, December 24, 2013 3:53:15 PM UTC-6, Johnsons in DE wrote:
Metallicow,
Thank you for your reply. Could you please provide a link to the GitHub page you are talkingabout? I saw from the screenshot you attached that you are using
wxPython Phoenix r74528, but I can’t find any place to download that
version from.Currently, I'm using r75338 from [http://wxpython.org/Phoenix/snapshot-builds/](http://wxpython.org/Phoenix/snapshot-builds/) . I had previously trieddownloading r75135 from there, but it had the same problems. The two
most recent downloads available on that page use wxWidgets 3.0.0, I
believe, but they are just the source, and I’d rather not have to
compile wxPython myself.Thank you.– Timothy Johnson
The snapshot are constant thing, they build by a bot time-based upon changes in the repos I think. You may not be able to get it now, but that shouldn’t matter anyway…
The number you are seeing in my pic is a reference to me and is located in the demo’s version.py. All it will do is complain you are not using a version of wx for the demo’s version build. This is wrong, but I haven’t changed it because I reference a snapshot point there for my reference.
Until robin merges/updates phoenix with my fixes, this number will not change, unless done manually to suppress annoying messagebox.
It references the Win32 Py33 snapshot I started with at that point in time and have since built upon. It can safely be ignored in your situation or just fix the number yourself if you don’t like the messagebox warning upon startup.
On Tuesday, December 24, 2013 3:53:15 PM UTC-6, Johnsons in DE wrote:
I saw from the screenshot you attached that you are usingwxPython Phoenix r74528, but I can’t find any place to download that
version from.
Just downloaded the snapshot build that you are using(wxPython_Phoenix-3.0.0.0-r75338-win32-py3.3.tar.gz) to do a quick test. Nope the main.py demo didn’t fireup/work.
Some of the individual demos work, but not all. Seems there are some issues with wx3.0 at the moment.
If you really want the compiled stuff from the revision I am working with It’s in the attachment.
This would be dropped into the wx dir also.
It is versioned wx-2.9.5-phoenix-r74528 for Win32Py33
The attachment is 5.36MB 7z Ultra compressed.
So if this doesn’t work in the meantime for you, then you are on your own until later down the line when the builds become unbroken again.
This often happens with buildbots builds because somewhere the tester might get a version inbetween dev commits that breaks something for so many revisions, etc.
Ex: They(head devs) might be in the middle of fixing something that may consist of 10 commits and break something temporarily and the bot decided to build somewhere inbetween these commits causing the end build to be a bork. Remember, that the bot doesn’t have a brain, it just does what it is told on a regular basis even if that may mean borked build.
wx-2.9.5-phoenix-r74528.7z (5.37 MB)
Metallicow,
Sorry for taking a while to respond. Thank you again for your help.
Using the archive you attached to your post, and the code from the
GitHub repositories you pointed me to, I was able to get wxPython
Phoenix to work. (Yeah!)
I am beginning to wonder if wxPython 3.0.0.0 does not work properly
on Windows XP. (We both, I believe, are running Win XP SP3).
I saw your posts on the wxPython-dev forum about your issues with
wxPython 3 Classic. Interestingly (to me), among the list of
scripts that crashed for you in the wxPython demo was
MultiChoiceDialog.py.
Robin suggested that something might be wrong with your
Python/wxPython installation, but I’m not so sure. I also tried
wxPython 3 Classic on my computer and had the same problems
you did.
So, I'm now wondering if the Phoenix snapshot builds aren't botched
after all. If wxPython 3 Classic isn’t working for us, why
should we expect the equivalent Phoenix build to?
I do have access to a Windows 7 computer, so if you'd like me to, I
could test wxPython 3 Classic and/or Phoenix on it to test my
speculations.
Thank you and happy new year.
-- Timothy Johnson
On Tuesday, December 24, 2013 8:54:51 PM UTC-5, Metallicow wrote:
Just downloaded the snapshot build that you are using(wxPython_Phoenix-3.0.0.0-r75338-win32-py3.3.tar.gz) to do a quick test. Nope the main.py demo didn’t fireup/work.
Some of the individual demos work, but not all. Seems there are some issues with wx3.0 at the moment.If you really want the compiled stuff from the revision I am working with It’s in the attachment.
This would be dropped into the wx dir also.
It is versioned wx-2.9.5-phoenix-r74528 for Win32Py33The attachment is 5.36MB 7z Ultra compressed.
So if this doesn’t work in the meantime for you, then you are on your own until later down the line when the builds become unbroken again.This often happens with buildbots builds because somewhere the tester might get a version inbetween dev commits that breaks something for so many revisions, etc.
Ex: They(head devs) might be in the middle of fixing something that may consist of 10 commits and break something temporarily and the bot decided to build somewhere inbetween these commits causing the end build to be a bork. Remember, that the bot doesn’t have a brain, it just does what it is told on a regular basis even if that may mean borked build.
Well, I wouldn’t go too far out. I run just about every OS on the face of the planet that I can…; manually with a brain, But I prefer XP.
Maybe in a week or so (the higher up the dev-chain) might get wind of the “glitches”.
Yes, reporting on these lists is a good thing to do overall(even if it is a simple question),
…tho devs(I am working on PHOENIX also if you didn’t know) have a hard time dealing with everything,
because of what most of us call the MIA or AWOL Effect(Real-Life) it produces on us at times.
The Best thing to do is keep excited about it(YES it works!), but there is still a lot to do yet.
Just because maybe wx3 has some problems at the moment shouldn’t bother most users much anyway.
One must realize that wxWidgets and wxPython are 2 seperate things(I have had problems with this…).
What we need is more wxPython Devs on board; Esp like Andrea. Devs On the wxPython Side of things…
It is a hectic process at times because maybe 20 people are working on 20 different things; etc.
go figure.
For example, you have an application, and would like to test.
Besides PY3 and the extras I have done and am working on with the demo…, If you don’t need exactly PY3 at the moment, then your best bet would be to STICK with classic ATM.
Yes, there are a few extra wow I like that, its new moments with PHOENIX, but for the most part…
… ATM… We are waiting on Robin to wrap up Classic 3.0(I assume), then move on to Phoenix, then integrate all the ahead work we(wxHelpers/wxDevelopers) have done for the projects sake,
then if he manages to have a good nights sleep after this then we can poke him about it again. *#@^&$
Cool! Gotta love it!. Drop a note on the wxPython-dev if ya are looking to run any of the fancy widgets on PHOENIX and might be troubled by that build(State the build- Ex: Maybe the retro3 one I gave ya).
SourceCoder is working as you well know…2.9.5 ATM tho and still developing.
DUH_NOTE: If you ever download a snapshot build as a tester or developer, and IT WORKS(alright for you), then keep a copy of it(teh archive with compiled stuff).
It may be your only working copy…
hmmm = [Remember wxWidgets is what builds wxPython]
If at all, at this point I would use the PHOENIX build I have (and is the cutting edge) until another snapshot comes out that works. Then maybe consider upgrading… (remember the wx.pth; you CAN have 1000wxVERSIONS installed and working all at the same time)
There are a lot of things to consider. Patience 1st. or help. Help and patience is prefered.
Thanks I could help out.
ugh…
Mooo
On Friday, December 27, 2013 8:07:24 PM UTC-6, Johnsons in DE wrote:
Metallicow,
Sorry for taking a while to respond. Thank you again for your help. Using the archive you attached to your post, and the code from theGitHub repositories you pointed me to, I was able to get wxPython
Phoenix to work. (Yeah!)I am beginning to wonder if wxPython 3.0.0.0 does not work properlyon Windows XP. (We both, I believe, are running Win XP SP3).
I saw your posts on the wxPython-dev forum about your issues withwxPython 3 Classic. Interestingly (to me), among the list of
scripts that crashed for you in the wxPython demo was
MultiChoiceDialog.py.Robin suggested that something might be wrong with yourPython/wxPython installation, but I’m not so sure. I also tried
wxPython 3 Classic on my computer and had the same problems
you did.So, I'm now wondering if the Phoenix snapshot builds aren't botchedafter all. If wxPython 3 Classic isn’t working for us, why
should we expect the equivalent Phoenix build to?I do have access to a Windows 7 computer, so if you'd like me to, Icould test wxPython 3 Classic and/or Phoenix on it to test my
speculations.Thank you and happy new year.