Re: wxPython Phoenix build fail ("Could not build python extensions"?) in pyenv 3.5.1 on Linux

Michael Freeman wrote:
> So, finally, I got past the current error. It was pyenv ! I posted
> them an issue: https://github.com/yyuu/pyenv/issues/691

Which was why I suggested trying it in a normal Python virtualenv or
venv that was created from the stock Python on your system, instead of
using pyenv's custom builds.

> But first I could just use wx in Windows but I chose Phoenix because
> its cross platform (nad it has to be Python 3 because of Blender). I
> don't want to restrict myself and other users to just Windows for the
> project. So what is the status of Phoenix ? Are these just a few
> random bugs or is Phoenix still some way off "prime time" as it were ?
> I don't mind helping with the development but will have to consider
> another Python GUI module eventually as I can't spend all my time on this.

The plan is to have an official alpha soonish, once I have completed
some of the things I have in progress right now.  The actual content of
the alpha won't be much different than what is in the snapshot builds
currently.  But the plan is to also start putting it on PyPI, so it will
end up being more of an implementation and test of a new release
process, and also a means of making a statement to the community that
Phoenix is usable. After the first (and maybe only?) alpha it will be
time to evaluate what features are still missing before making a beta
release and those will be worked on next.

For anybody wanting to help out, here are some things currently on my radar:

 * The wx.lib modules and subpackages have had a lot of work already for
porting to Phoenix and also adding some docstrings and such, but I think
there is still more work to be done there.  I've seen some errors
related to Py3 compatibility here and there so it would be good to have
somebody go over all of the modules testing and fixing any Py3 issues
that are discovered.  I haven't reviewed the wx.lib.agw modules much at
all yet, so that would be a good place to start. Another place that
needs some attention is the wx.lib.masked package.

 * There is also the list in the TODO.rst file in the source tree.  Some
of those are just nice-to-haves, some are more important.

 * I'm currently working on adding wrappers for the propgrid module. 
It's mostly done except for some documentation generation tweaks.
However, I've never actually used it myself in an application so when my
current work is merged it would be good for somebody with some
experience with propgrid in Classic to give the API a look, port the
demo or whatever, and determine if there are any greater than expected
compatibility breaks.


-- 
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 [email protected].
For more options, visit https://groups.google.com/d/optout.