How to best indentify Phoenix from Classic from calling application

Robbin or ?"

I wrote a modified backend for Almar Klein’s visvis (graphics plotting lib) which selects the proper wxPython API as follows:

    if "phoenix" in wx.version():
        self._phoenix = True
        self._ProcessEvents = self._ProcessEventsPhoenix
    else:
        self._phoenix = False
        self._ProcessEvents = self._ProcessEventsClassic 

The question we had is: will the string “phoenix” always be included in the return from wx.version or is there a better way to tell if one is using the Phoenix module over classic?

Thanks,
Keith

Keith Smith wrote:

The question we had is: will the string "phoenix" always be included in
the return from wx.version or is there a better way to tell if one is
using the Phoenix module over classic?

No, it may not always be in the wx.version() string, but it will always be in the wx.PlatformInfo tuple.

···

--
Robin Dunn
Software Craftsman

Well, maybe…
Not completely sure on robins ‘phoenix’ codename, but if there is another one it will probably be “phoenix2” or some other ‘firebird’ codename. Maybe Chimera or Unicorn
Note sure if Py2 and Py3 have “codenames”. I recall Py3 as codename “py3000”(love the comical references… but…),…
http://en.wikipedia.org/wiki/Phoenix_(mythology)
http://imageshack.us/a/img109/2641/bannerwindowpreview.png

So just guess that if there are any major compatibility issues arising out out say,
“a conversion from PY3 to PY4” then it will probably change in the future after PY3 that it happens postpost,
and as the legend goes “A phoenix is reborn through it’s ashes”, so the rumor is wxPython4 is codenamed “firebird chimera unicorn donkey kong”**.

** just joking Robin :slight_smile:

The next wxpy codename is “TopSecretConfidential” ATM. pretty simple huh!