Is Phoenix (wxPython for Python 3.x) going to run (or does it already do that) under Python 3.3 Beta 1?
Hi,
···
On 8 July 2012 11:42, Boštjan Mejak wrote:
Is Phoenix (wxPython for Python 3.x) going to run (or does it already do
that) under Python 3.3 Beta 1?
I don't see why not. I don't recall Python 3.3 introducing
particularly weird stuff, so I believe Phoenix can already be compiled
against Python 3.3. The Phoenix binaries [1], however, are still not
there (as there is no Python 3.3 yet, just a beta).
[1] Index of /Phoenix/snapshot-builds
--
Andrea.
"Imagination Is The Only Weapon In The War Against Reality."
http://xoomer.alice.it/infinity77/
# ------------------------------------------------------------- #
def ask_mailing_list_support(email):
if mention_platform_and_version() and include_sample_app():
send_message(email)
else:
install_malware()
erase_hard_drives()
# ------------------------------------------------------------- #
Thanks, Andrea. 
Which version of SWIG is Phoenix going to be compiled with?
No SWIG in Phoenix 
One of the biggest differences between wxPython Classic and Phoenix is
the way the bridge between C++ and Python (the binding) is generated,
and Phoenix is based on sip:
http://riverbankcomputing.co.uk/software/sip/intro
It appears to be significantly easier to use and maintain than SWIG,
but I am no expert in this area. The Phoenix SVN sources make it
relatively easy (at least on Windows) to compile Phoenix for Python
2.7 and 3.2.
Andrea.
"Imagination Is The Only Weapon In The War Against Reality."
http://xoomer.alice.it/infinity77/
# ------------------------------------------------------------- #
def ask_mailing_list_support(email):
if mention_platform_and_version() and include_sample_app():
send_message(email)
else:
install_malware()
erase_hard_drives()
# ------------------------------------------------------------- #
···
On 8 July 2012 14:13, Boštjan Mejak wrote:
Thanks, Andrea.
Which version of SWIG is Phoenix going to be compiled with?
Python 3.3 will require using a newer MSVC for Windows builds, and I'll likely need to do some tweaks in the build scripts to support that. But other than that I expect that it should just work.
···
On 7/8/12 3:27 AM, Andrea Gavana wrote:
Hi,
On 8 July 2012 11:42, Boštjan Mejak wrote:
Is Phoenix (wxPython for Python 3.x) going to run (or does it already do
that) under Python 3.3 Beta 1?I don't see why not. I don't recall Python 3.3 introducing
particularly weird stuff, so I believe Phoenix can already be compiled
against Python 3.3. The Phoenix binaries [1], however, are still not
there (as there is no Python 3.3 yet, just a beta).
--
Robin Dunn
Software Craftsman
Another nice thing related to this that I can't believe I didn't think of years ago is that the build will download the proper version of sip and the other tools for you the first time you do the build, and will update it when the required version changes. So you don't have to worry about getting and installing the right version yourself.
···
On 7/8/12 5:21 AM, Andrea Gavana wrote:
On 8 July 2012 14:13, Boštjan Mejak wrote:
Thanks, Andrea.
Which version of SWIG is Phoenix going to be compiled with?
No SWIG in Phoenix
One of the biggest differences between wxPython Classic and Phoenix is
the way the bridge between C++ and Python (the binding) is generated,
and Phoenix is based on sip:http://riverbankcomputing.co.uk/software/sip/intro
It appears to be significantly easier to use and maintain than SWIG,
but I am no expert in this area. The Phoenix SVN sources make it
relatively easy (at least on Windows) to compile Phoenix for Python
2.7 and 3.2.
--
Robin Dunn
Software Craftsman