What is the approved way to detect Phoenix?

wxPython Users
1

What is the approved way in a program to determine whether the classic or Phoenix version of wxPython has been imported? At the moment, classic wx.VERSION yields (2, 9, 4, 0, ‘’) and Phoenix gives (2, 9, 5, 80, ‘’), the 80 indicating that this is not a real release but just a nightly build. Will it be the case in the future that the classic version will never go beyond 2.9.4?

And while I’m at it, something that I’ve looked for but not found: Is there an estimate/plan for when there will be real releases of Phoenix? It is the case that the current nightly builds are entirely adequate for my own purposes, because VPython currently needs only very central elements of wxPython, but presumably when there are real releases there will be a version for 64-bit Windows Python 3.x, which so far I’ve been unable to build myself.

2

Hi Bruce,

What is the approved way in a program to determine whether the classic or
Phoenix version of wxPython has been imported? At the moment, classic
wx.VERSION yields (2, 9, 4, 0, '') and Phoenix gives (2, 9, 5, 80, ''), the
80 indicating that this is not a real release but just a nightly build. Will
it be the case in the future that the classic version will never go beyond
2.9.4?

I would go with something like this:

C:\Users\Andrea>python
Python 2.7.2 (default, Jun 12 2011, 14:24:46) [MSC v.1500 64 bit
(AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.

import wx
wx.version()

'2.9.4.0 msw (classic)'

... after changing wx.pth to point to Phoenix... :

C:\Users\Andrea>python
Python 2.7.2 (default, Jun 12 2011, 14:24:46) [MSC v.1500 64 bit
(AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.

import wx
wx.version()

'2.9.5.80 msw (phoenix)'

So, the "classic" and "phoenix" strings will (should) always be there.

And while I'm at it, something that I've looked for but not found: Is there
an estimate/plan for when there will be real releases of Phoenix? It is the
case that the current nightly builds are entirely adequate for my own
purposes, because VPython currently needs only very central elements of
wxPython, but presumably when there are real releases there will be a
version for 64-bit Windows Python 3.x, which so far I've been unable to
build myself.

I don't know what Robin's plans are, although much of wxPython Classic
is already available in Phoenix. Pretty much all the wrapped classes
are there, but we will need some manpower to port what is left of
wx.lib. AGW should almost be there (only a few un-ported widgets
exist), but other items are still outstanding. The biggest ones I can
think of are FloatCanvas and pubsub, but pretty much the entire wx.lib
needs to be addressed.

Andrea.

"Imagination Is The Only Weapon In The War Against Reality."

# ------------------------------------------------------------- #
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 16 February 2013 20:53, Bruce Sherwood wrote:

3

Andrea Gavana wrote:

Hi Bruce,

What is the approved way in a program to determine whether the classic or
Phoenix version of wxPython has been imported? At the moment, classic
wx.VERSION yields (2, 9, 4, 0, '') and Phoenix gives (2, 9, 5, 80, ''), the
80 indicating that this is not a real release but just a nightly build. Will
it be the case in the future that the classic version will never go beyond
2.9.4?

I would go with something like this:

C:\Users\Andrea>python
Python 2.7.2 (default, Jun 12 2011, 14:24:46) [MSC v.1500 64 bit
(AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.

import wx
wx.version()

'2.9.4.0 msw (classic)'

... after changing wx.pth to point to Phoenix... :

C:\Users\Andrea>python
Python 2.7.2 (default, Jun 12 2011, 14:24:46) [MSC v.1500 64 bit
(AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.

import wx
wx.version()

'2.9.5.80 msw (phoenix)'

So, the "classic" and "phoenix" strings will (should) always be there.

Maybe not. But 'phoenix' will always be in wx.PlatformInfo for Phoenix builds, so that will probably be a better choice.

     if 'phoenix' in wx.PlatformInfo:
         doSomething()
     else:
         doSomethingElse()

Note that 'classic' will not be in wx.PlatformInfo since it has never been there before. If somebody tested for 'classic' on an older version of classic then they could get a false-negative.

And while I'm at it, something that I've looked for but not found: Is there
an estimate/plan for when there will be real releases of Phoenix? It is the
case that the current nightly builds are entirely adequate for my own
purposes, because VPython currently needs only very central elements of
wxPython, but presumably when there are real releases there will be a
version for 64-bit Windows Python 3.x, which so far I've been unable to
build myself.

I don't know what Robin's plans are, although much of wxPython Classic
is already available in Phoenix. Pretty much all the wrapped classes
are there, but we will need some manpower to port what is left of
wx.lib. AGW should almost be there (only a few un-ported widgets
exist), but other items are still outstanding. The biggest ones I can
think of are FloatCanvas and pubsub, but pretty much the entire wx.lib
needs to be addressed.

There really can't be a very reliable timeline, at least not until we get really close to being ready. It mainly depends how busy I am with the day job, and lately it's been very busy. When I have spare brain cycles then I'm able to jump forward again, but otherwise progress is mostly a trickle.

···

On 16 February 2013 20:53, Bruce Sherwood wrote:

--
Robin Dunn
Software Craftsman

4

Thanks for the info, both about PlatformInfo and about release possibilities.

I’ll use if ‘phoenix’ in wx.PlatformInfo in the VPython library.

···

On Sat, Feb 16, 2013 at 3:06 PM, Robin Dunn robin@alldunn.com wrote:

Andrea Gavana wrote:

Hi Bruce,

On 16 February 2013 20:53, Bruce Sherwood wrote:

What is the approved way in a program to determine whether the classic or

Phoenix version of wxPython has been imported? At the moment, classic

wx.VERSION yields (2, 9, 4, 0, ‘’) and Phoenix gives (2, 9, 5, 80, ‘’), the

80 indicating that this is not a real release but just a nightly build. Will

it be the case in the future that the classic version will never go beyond

2.9.4?

I would go with something like this:

C:\Users\Andrea>python

Python 2.7.2 (default, Jun 12 2011, 14:24:46) [MSC v.1500 64 bit

(AMD64)] on win32

Type “help”, “copyright”, “credits” or “license” for more information.

import wx

wx.version()
‘2.9.4.0 msw (classic)’

… after changing wx.pth to point to Phoenix… :

C:\Users\Andrea>python

Python 2.7.2 (default, Jun 12 2011, 14:24:46) [MSC v.1500 64 bit

(AMD64)] on win32

Type “help”, “copyright”, “credits” or “license” for more information.

import wx

wx.version()
‘2.9.5.80 msw (phoenix)’

So, the “classic” and “phoenix” strings will (should) always be there.

Maybe not. But ‘phoenix’ will always be in wx.PlatformInfo for Phoenix builds, so that will probably be a better choice.

if 'phoenix' in wx.PlatformInfo:

    doSomething()

else:

    doSomethingElse()

Note that ‘classic’ will not be in wx.PlatformInfo since it has never been there before. If somebody tested for ‘classic’ on an older version of classic then they could get a false-negative.

And while I’m at it, something that I’ve looked for but not found: Is there

an estimate/plan for when there will be real releases of Phoenix? It is the

case that the current nightly builds are entirely adequate for my own

purposes, because VPython currently needs only very central elements of

wxPython, but presumably when there are real releases there will be a

version for 64-bit Windows Python 3.x, which so far I’ve been unable to

build myself.

I don’t know what Robin’s plans are, although much of wxPython Classic

is already available in Phoenix. Pretty much all the wrapped classes

are there, but we will need some manpower to port what is left of

wx.lib. AGW should almost be there (only a few un-ported widgets

exist), but other items are still outstanding. The biggest ones I can

think of are FloatCanvas and pubsub, but pretty much the entire wx.lib

needs to be addressed.

There really can’t be a very reliable timeline, at least not until we get really close to being ready. It mainly depends how busy I am with the day job, and lately it’s been very busy. When I have spare brain cycles then I’m able to jump forward again, but otherwise progress is mostly a trickle.

–

Robin Dunn

Software Craftsman

http://wxPython.org

–

You received this message because you are subscribed to the Google Groups “wxPython-users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to wxpython-users+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.