Brendan Barnwell wrote:
I've seen these various posts about the "Phoenix" project which
supposedly will make wxPython available for Python 3. Those posts seem
to go back a ways in time. I see that there is a snapshot builds
directory, but it doesn't look like it has binary installers, and I see
various mailing list messages about Phoenix being incomplete. I use a
delightful GUI library called Dabo that wraps wxPython, and Dabo is
waiting on wxPython to upgrade to Python 3 before Dabo can follow suit.
Without wanting to seem like a nag, I'm just wondering what the status
is as far as the transition of Python 3-compatible wxPython from a
bleeding-edge development version to something that is actually released
for the average Python programmer to use.Let's imagine a day when I can go to the front page of wxpython.org and
see a notice that an official release of wxPython has been made which
supports Python 3. Does anyone have a ballpark guess on how far away
that day is? If you had to choose between a month, six months, a year,
and two years, which do you think is most accurate?
If you tortured me into giving an answer I would say six months, but it would just be a SWAG.
However there isn't much reason to not start using the daily builds now, at least to the point of testing your code to see what is still missing and to give you a better idea of the effort needed to port to Phoenix and Python3. You can untar the snapshots and move the wx folder to wherever you like on your computer and use PYTHONPATH to have it be imported instead of the release version. Or use a virtualenv and put it there. Or manually install it as 2.9.6 into Python's site-packages as Werner suggested and use wxselect.
···
--
Robin Dunn
Software Craftsman