Is wxPython Phoenix release version exist?

wxPython Users
1

I can’t find wxPython Phoenix release version.

I found only develop version. (http://wxpython.org/Phoenix/snapshot-builds/)

Is wxPython Phoenix release version exist?

2

These are all 3.0:
http://wxpython.org/download.php

···

On Monday, May 12, 2014 4:59:38 PM UTC-7, hudif wrote:

I can’t find wxPython Phoenix release version.

I found only develop version. (http://wxpython.org/Phoenix/snapshot-builds/)

Is wxPython Phoenix release version exist?

3

I think wxPython Phoenix, not wx Python.

2014年5月15日木曜日 10時18分28秒 UTC+9 Nathan McCorkle:

···

These are all 3.0:
http://wxpython.org/download.php

On Monday, May 12, 2014 4:59:38 PM UTC-7, hudif wrote:

I can’t find wxPython Phoenix release version.

I found only develop version. (http://wxpython.org/Phoenix/snapshot-builds/)

Is wxPython Phoenix release version exist?

4

isn’t phoenix just the code-name? I thought since with the 3.0 update the internals changed wildly, that it was worthy of a name in addition to a new version number.

···

On Wednesday, May 14, 2014 7:17:27 PM UTC-7, hudif wrote:

I think wxPython Phoenix, not wx Python.

2014年5月15日木曜日 10時18分28秒 UTC+9 Nathan McCorkle:

These are all 3.0:
http://wxpython.org/download.php

On Monday, May 12, 2014 4:59:38 PM UTC-7, hudif wrote:

I can’t find wxPython Phoenix release version.

I found only develop version. (http://wxpython.org/Phoenix/snapshot-builds/)

Is wxPython Phoenix release version exist?

5

The 3.0 Update reflects the fact that wxPython 3.0 is the python
wrapper for wxWidgets 3.0 - This was a major update but not the
Project Phoenix - that is distinguished by if you run:
$ python -c “import wx;print wx.version();”
You will get a response such as:
3.0.0.0 gtk2 (classic)
The Phoenix detail that in the Project Phoenix implementation
wxPython, it’s docstrings and the documentation will all be
generated in a totally different manner. This will have a number of
advantages amongst:

···

On 15/05/14 05:42, Nathan McCorkle
wrote:

    isn't phoenix just the code-name? I thought since

with the 3.0 update the internals changed wildly, that it was
worthy of a name in addition to a new version number.

Classic
Vs. Phoenix

Project
Goals 

  •     Less manual intervention so wxPython releases can be hot on
    the heels of wxWidgets releases
  •     wxPython specific documentation package rather than the
    current C++ with some manually added and sometimes not updated
    notes so no guess which of the overloaded functions is the
    correct one, remember to put the . after wx etc.
  • Python3 support out of the box
  • Possibly distribute as eggs.
  • Better exception handling
    As you can guess there is a lot of work involved, and
    some compatibility issues, so the “mainstream” wxPython is still
    “classic” for the moment. The wiki details current progress and
    there are daily snapshots to try but I can not find, * (and did
    not really expect)*, a hard and fast release date.
  •    Hope I have given a reasonable summary without stepping on

anybodies toes* *and appologies if I have miss-spoken.
*

Gadget/Steve
**

6

The only thing I would add is that I think Robin is adding support for Python wheels and there is a possibility that egg support will be dropped.

  • Mike
···

On Thursday, May 15, 2014 12:24:37 AM UTC-5, Gadget Steve wrote:

  On 15/05/14 05:42, Nathan McCorkle > wrote:

    isn't phoenix just the code-name? I thought since

with the 3.0 update the internals changed wildly, that it was
worthy of a name in addition to a new version number.

The 3.0 Update reflects the fact that wxPython 3.0 is the python

wrapper for wxWidgets 3.0 - This was a major update but not the
Project Phoenix - that is distinguished by Classic
Vs. Phoenix if you run:

$ python -c "import wx;print wx.version();"



You will get a response such as:



3.0.0.0 gtk2 (classic)



The Phoenix [      Project

Goals ](ProjectPhoenix/ProjectGoals - wxPyWiki) detail that in the Project Phoenix implementation
wxPython, it’s docstrings and the documentation will all be
generated in a totally different manner. This will have a number of
advantages amongst:

  •     Less manual intervention so wxPython releases can be hot on
    the heels of wxWidgets releases
  •     wxPython specific documentation package rather than the
    current C++ with some manually added and sometimes not updated
    notes so no guess which of the overloaded functions is the
    correct one, remember to put the . after wx etc.
  • Python3 support out of the box
  • Possibly distribute as eggs.
  • Better exception handling
    As you can guess there is a lot of work involved, and
    some compatibility issues, so the “mainstream” wxPython is still
    “classic” for the moment. The wiki details current progress and
    there are daily snapshots to try but I can not find, * (and did
    not really expect)*, a hard and fast release date.
  •    Hope I have given a reasonable summary without stepping on

anybodies toes* *and appologies if I have miss-spoken.
*

Gadget/Steve
**

7

…
Has added wheel support and for a little while now the snapshots
are only in wheel format.
to install the latest:
pip install -U --pre -f wxPython_Phoenix
Werner

···

Hi,

  On 5/15/2014 17:01, Mike Driscoll wrote:

    On Thursday, May 15, 2014 12:24:37 AM UTC-5, Gadget Steve wrote:

On 15/05/14 05:42, Nathan McCorkle wrote:

            isn't phoenix just the code-name? I thought

since with the 3.0 update the internals changed wildly,
that it was worthy of a name in addition to a new
version number.

        The 3.0 Update reflects the fact that wxPython 3.0 is the

python wrapper for wxWidgets 3.0 - This was a major update
but not the Project Phoenix - that is distinguished by Classic Vs. Phoenix if you run:

        $ python -c "import wx;print wx.version();"



        You will get a response such as:



        3.0.0.0 gtk2 (classic)



        The Phoenix [Project Goals ](http://wiki.wxpython.org/ProjectPhoenix/ProjectGoals)            detail that in the Project

Phoenix implementation wxPython, it’s docstrings and the
documentation will all be generated in a totally different
manner. This will have a number of advantages amongst:

  •             Less manual intervention so wxPython releases can be
    hot on the heels of wxWidgets releases
  •             wxPython specific documentation package rather than
    the current C++ with some manually added and sometimes
    not updated notes so no guess which of the overloaded
    functions is the correct one, remember to put the .
    after wx etc.
  • Python3 support out of the box
  • Possibly distribute as eggs.
  • Better exception handling
    As you can guess there is a lot of work involved,
    and some compatibility issues, so the “mainstream”
    wxPython is still “classic” for the moment. The wiki
    details current progress and there are daily snapshots to
    try but I can not find, (and did not really expect) ,
    a hard and fast release date.
  •            Hope I have given a reasonable summary without

stepping on anybodies toes* * and appologies if I
have miss-spoken.
*

Gadget/Steve
**

      The only thing I would add is that I think Robin is adding

support for Python wheels and there is a possibility that egg
support will be dropped.

http://wxpython.org/Phoenix/snapshot-builds/

http://wxpython.org/Phoenix/snapshot-builds/