The Phoenix snapshot builds stopped for several months, then restarted, but seem to have stopped again (none in the last month). There haven’t been any Phoenix commits since August 11 on https://github.com/wxWidgets/Phoenix.git and there are 13 outstanding pull requests, but there is continuing work on the wx 3.0 branch at https://github.com/wxWidgets/wxWidgets.git.
Would someone please give a status update?
Thanks,
Greg
A related question: Will builds of Phoenix for Python 3.5 be available soon?
I would think there’s probably more work involved in supporting 3.5 than there was for 3.4, because 3.5 is built with a newer Windows compiler. I expect this means that different versions of the wxWidgets DLLs need to be used.
Greg Couch wrote:
The Phoenix snapshot builds stopped for several months, then restarted,
but seem to have stopped again (none in the last month). There haven't
been any Phoenix commits since August 11 on
GitHub - wxWidgets/Phoenix: wxPython's Project Phoenix. A new implementation of wxPython, better, stronger, faster than he was before. and there are 13 outstanding
pull requests, but there is continuing work on the wx 3.0 branch at
GitHub - wxWidgets/wxWidgets: Cross-Platform C++ GUI Library.Would someone please give a status update?
Just hiatus. The day job is keeping me real busy, and family and other IRL things have picked up as well, and it's sometimes hard to find large enough blocks of time to be able to switch mental gears and focus on Phoenix. I'm still committed to moving Phoenix forward, it's just moving very slowly lately. I've been doing some behind the scenes things recently with my build environments, working on a couple issues deep in the code, and buildbot updates.
I encourage all to continue submitting PRs, as they are the easiest way for me to track and merge fixes and enhancements and will help me to be the most efficient when I do have time to focus on them.
--
Robin Dunn
Software Craftsman
tjohnson wrote:
A related question: Will builds of Phoenix for Python 3.5 be available soon?
I would think there's probably more work involved in supporting 3.5 than
there was for 3.4, because 3.5 is built with a newer Windows compiler. I
expect this means that different versions of the wxWidgets DLLs need to
be used.
Yeah, I still need to get the new compiler and get it set up on the Windows build machines. In the past I've had 1 year MSDN subscriptions donated to me and that is how I've gotten the compiler upgrades.
I haven't been following Python 3.5 and VisStudio 2015 news very closely, has anybody heard if there is enough included with the free VisStudio Community edition for building and debugging Python extensions? (In the past the Express versions were usually crippled in some way, like no 64-bit, no optimizations, or no command-line compiler and tools, etc.)
--
Robin Dunn
Software Craftsman
tjohnson wrote:
A related question: Will builds of Phoenix for Python 3.5 be available soon?
I would think there's probably more work involved in supporting 3.5 than
there was for 3.4, because 3.5 is built with a newer Windows compiler. I
expect this means that different versions of the wxWidgets DLLs need to
be used.Yeah, I still need to get the new compiler and get it set up on the Windows build machines. In the past I've had 1 year MSDN subscriptions donated to me and that is how I've gotten the compiler upgrades.
I haven't been following Python 3.5 and VisStudio 2015 news very closely, has anybody heard if there is enough included with the free VisStudio Community edition for building and debugging Python extensions? (In the past the Express versions were usually crippled in some way, like no 64-bit, no optimizations, or no command-line compiler and tools, etc.)
As of 2013 most of the restrictions they used to impose in the free version were gone, definitely I know 64 bit and command line tools are built in now. It should be a much smoother experience than it was in the good old days. 
Regards,
Kevin
On Sep 22, 2015, at 11:06 AM, Robin Dunn <robin@alldunn.com> wrote:
--
Robin Dunn
Software Craftsman
http://wxPython.org--
You received this message because you are subscribed to the Google Groups "wxPython-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wxPython-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I haven't been following Python 3.5 and VisStudio 2015 news very closely, has anybody heard if there is enough included with the free VisStudio Community edition for building and debugging Python extensions? (In the past the Express versions were usually crippled in some way, like no 64-bit, no optimizations, or no command-line compiler and tools, etc.)
I think it's gotten a lot better, but you never know till you try....
-CHB
If I may ask, what are the criteria for a PyPI release of Phoenix, and how far are we from there?
After all, an internal or proprietary project can bundle snapshot releases in a frozen application, but open-source projects can’t really do that.
Hi,
On 9/23/2015 8:55, Andreu Botella wrote:
If I may ask, what are the criteria for a PyPI release of Phoenix, and how far are we from there?
You know you can install with pip, so why should time be spent to release onto PyPi at this point?
http://wiki.wxpython.org/How%20to%20install%20wxPython#Installing_wxPython-Phoenix_using_pip
Werner
The fact that pip simply won’t let you install from a HTTP-only host without a command-line flag seems enough reason, since it means you just use setup.py or requirements.txt normally. But more generally, because it’s the standard convention in Python.
On Wednesday, September 23, 2015 at 9:36:03 AM UTC+2, werner wrote:
Hi,
On 9/23/2015 8:55, Andreu Botella wrote:
If I may ask, what are the criteria for a PyPI release of Phoenix, and
how far are we from there?You know you can install with pip, so why should time be spent to
release onto PyPi at this point?http://wiki.wxpython.org/How%20to%20install%20wxPython#Installing_wxPython-Phoenix_using_pip
Werner
Once you’ve done the EIGHT GIG installation core Python 3.5 builds fine, but there are known problems building extensions, see http://code.activestate.com/lists/python-list/691821/
On Tuesday, September 22, 2015 at 7:06:41 PM UTC+1, Robin Dunn wrote:
tjohnson wrote:
A related question: Will builds of Phoenix for Python 3.5 be available soon?
I would think there’s probably more work involved in supporting 3.5 than
there was for 3.4, because 3.5 is built with a newer Windows compiler. I
expect this means that different versions of the wxWidgets DLLs need to
be used.
Yeah, I still need to get the new compiler and get it set up on the
Windows build machines. In the past I’ve had 1 year MSDN subscriptions
donated to me and that is how I’ve gotten the compiler upgrades.I haven’t been following Python 3.5 and VisStudio 2015 news very
closely, has anybody heard if there is enough included with the free
VisStudio Community edition for building and debugging Python
extensions? (In the past the Express versions were usually crippled in
some way, like no 64-bit, no optimizations, or no command-line compiler
and tools, etc.)–
Robin DunnSoftware Craftsman
Too me Phoenix is still 'too much' work in progress and putting it up on PyPi will increase support questions to this and to the wxpython-users list. Is this really what the project needs at this point?
I think time is better spent on fixing things and to get the project into better shape.
Just my 0.02€
Werner
On 9/23/2015 11:01, Andreu Botella wrote:
The fact that pip simply won't let you install from a HTTP-only host without a command-line flag seems enough reason, since it means you just use setup.py or requirements.txt normally. But more generally, because it's the standard convention in Python.
I think that Phoenix should be more accessible than it is now. I mean:
Marco
On Wednesday, September 23, 2015 at 12:54:11 PM UTC+2, werner wrote:
On 9/23/2015 11:01, Andreu Botella wrote:
The fact that pip simply won’t let you install from a HTTP-only host
without a command-line flag seems enough reason, since it means you
just use setup.py or requirements.txt normally. But more generally,
because it’s the standard convention in Python.Too me Phoenix is still ‘too much’ work in progress and putting it up on
PyPi will increase support questions to this and to the wxpython-users
list. Is this really what the project needs at this point?I think time is better spent on fixing things and to get the project
into better shape.Just my 0.02€
Werner
+1
2015-10-14 10:46 GMT-05:00 Marco Prosperi marcoprosperi347@gmail.com:
I think that Phoenix should be more accessible than it is now. I mean:
- there should be a direct link to Phoenix pages on wxpyhton main page
- a clear info to install it (I’ve found the working command to install phoenix wheel after reading wxpy-dev)
- an easy to find phoenix-version wxpython-demo application (where is it?). With this I could see what is not working and would contribute to migrate the lib modules I use most
Marco
On Wednesday, September 23, 2015 at 12:54:11 PM UTC+2, werner wrote:
On 9/23/2015 11:01, Andreu Botella wrote:
The fact that pip simply won’t let you install from a HTTP-only host
without a command-line flag seems enough reason, since it means you
just use setup.py or requirements.txt normally. But more generally,
because it’s the standard convention in Python.Too me Phoenix is still ‘too much’ work in progress and putting it up on
PyPi will increase support questions to this and to the wxpython-users
list. Is this really what the project needs at this point?I think time is better spent on fixing things and to get the project
into better shape.Just my 0.02€
Werner
–
You received this message because you are subscribed to the Google Groups “wxPython-dev” group.
To unsubscribe from this group and stop receiving emails from it, send an email to wxPython-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Saludos / Best regards
Mario Lacunza
Email:: mlacunza@gmail.com
Personal Website:: http://www.lacunza.biz/
Hosting:: http://mlv-host.com/
Mascotas Perdidas:: http://mascotas-perdidas.com/
Skype: mlacunzav
Lima - Peru
...
- an easy to find phoenix-version wxpython-demo application (where is it?). With this I could see what is not working and would contribute to migrate the lib modules I use most
The demo is in the repo:
Note that most work needs to be done in wx.lib, modules which have been worked on (ported, documented) have a tag (e.g.: # Tags: phoenix-port, unittest, documented, py3-port) at the beginning. Code should be changed in a way that it runs on Py2.7 and 3.2+, for this the six library (it is installed with Phoenix) is often used. Modules should have a unittest, even if it is very minimal to start with.
Werner
On 10/14/2015 17:46, Marco Prosperi wrote:
I installed the phoenix wheel for python 3.4 some days ago and run successfully a little sample of mine (on windows, 64 bit). With the demo just downloaded I get this demotivating exception:
C:\Users\Marco\Downloads\Phoenix-master\Phoenix-master\demo>c:\python34\python.e
xe demo.py
Traceback (most recent call last):
File “c:\python34\lib\site-packages\wx\core.py”, line 1955, in Notify
self.notify()
File “c:\python34\lib\site-packages\wx\core.py”, line 3032, in Notify
self.result = self.callable(*self.args, **self.kwargs)
File “C:\Users\Marco\Downloads\Phoenix-master\Phoenix-master\demo\Main.py”, li
ne 2869, in ShowMain
frame = wxPythonDemo(None, “wxPython: (A Demonstration)”)
File “C:\Users\Marco\Downloads\Phoenix-master\Phoenix-master\demo\Main.py”, li
ne 1836, in init
self.LoadDemo(self.overviewText)
File “C:\Users\Marco\Downloads\Phoenix-master\Phoenix-master\demo\Main.py”, li
ne 2255, in LoadDemo
self.UpdateNotebook(0)
File “C:\Users\Marco\Downloads\Phoenix-master\Phoenix-master\demo\Main.py”, li
ne 2381, in UpdateNotebook
UpdatePage(self.codePage, “Demo Code”)
File “C:\Users\Marco\Downloads\Phoenix-master\Phoenix-master\demo\Main.py”, li
ne 2352, in UpdatePage
if nb.GetPageText(i) == pageText:
wx._core.wxAssertionError: C++ assertion “((nPage) < GetPageCount())” failed at
…..\src\msw\notebook.cpp(448) in wxNotebook::GetPageText(): notebook page out
of range
On Wednesday, October 14, 2015 at 6:05:04 PM UTC+2, werner wrote:
On 10/14/2015 17:46, Marco Prosperi wrote:
…
- an easy to find phoenix-version wxpython-demo application (where is
it?). With this I could see what is not working and would contribute
to migrate the lib modules I use mostThe demo is in the repo:
https://github.com/wxWidgets/Phoenix/commits/master
Note that most work needs to be done in wx.lib, modules which have been
worked on (ported, documented) have a tag (e.g.: # Tags:
phoenix-port, unittest, documented, py3-port) at the beginning. Code
should be changed in a way that it runs on Py2.7 and 3.2+, for this the
six library (it is installed with Phoenix) is often used. Modules
should have a unittest, even if it is very minimal to start with.Werner
I just tried it on Windows 8.1 with Py 3.4 (32 bit) with master branch and I don't see this error. Now what snapshot are you using? I am on 1820+49a8884
Werner
P.S.
Maybe start a new thread instead of keeping this going for ........
On 10/14/2015 19:15, Marco Prosperi wrote:
I installed the phoenix wheel for python 3.4 some days ago and run successfully a little sample of mine (on windows, 64 bit). With the demo just downloaded I get this demotivating exception: