Hi. I am a PyPy dev. Today I tried building wxPython Phoenix using PyPy,
and would like to share my experience :).
It took me a while to find the github repo, the wiki and web site do not
seem to mention it AFAICT. In fact, the buildbot instructions here
https://wiki.wxpython.org/ProjectPhoenix/BuildbotSlave tricked me into
thinking that SVN was stil the preferred method of source control for
the project. But once I found the github repo
https://github.com/wxWidgets/Phoenix everything became easier.
Since I am using a dev version of PyPy (not packaged by the Debian
maintainer, rather the nightly HEAD), I needed to roll my own
pypy-config based on the python27-config script.
Of course, the build immediately crashed since our C-API compatibility
is not yet good enough. We seem to have some badly declared function
signatures that do not match CPython, I will be fixing these over the
next few weeks, and may need to submit patches or fixes for too
heavy-duty use of c pointers that I cannot fix on the PyPy side of things.
I would love to get the wxPython toolkit working under PyPY, so I hope
there are not too many patches needed.
FWIW, we did try to use CFFI instead of the C-API a few years back
during a Google Summer of Code, the results are languishing on
https://bitbucket.org/waedt/wxpython_cffi.
So thanks for wxPython, and stay tuned, hopefully I can make some
progress here
Matti
Matti,
I think you sent this to the wrong mailing list? This went to
matplotlib-devel, not the wxpython list 
That aside, getting wxPython working seems like good progress from the POV
of mpl + pypy!
Tom
···
On Wed, Oct 19, 2016 at 3:05 PM Matti Picus <matti.picus at gmail.com> wrote:
Hi. I am a PyPy dev. Today I tried building wxPython Phoenix using PyPy,
and would like to share my experience :).
It took me a while to find the github repo, the wiki and web site do not
seem to mention it AFAICT. In fact, the buildbot instructions here
ProjectPhoenix/BuildbotSlave - wxPyWiki tricked me into
thinking that SVN was stil the preferred method of source control for
the project. But once I found the github repo
GitHub - wxWidgets/Phoenix: wxPython's Project Phoenix. A new implementation of wxPython, better, stronger, faster than he was before. everything became easier.
Since I am using a dev version of PyPy (not packaged by the Debian
maintainer, rather the nightly HEAD), I needed to roll my own
pypy-config based on the python27-config script.
Of course, the build immediately crashed since our C-API compatibility
is not yet good enough. We seem to have some badly declared function
signatures that do not match CPython, I will be fixing these over the
next few weeks, and may need to submit patches or fixes for too
heavy-duty use of c pointers that I cannot fix on the PyPy side of things.
I would love to get the wxPython toolkit working under PyPY, so I hope
there are not too many patches needed.
FWIW, we did try to use CFFI instead of the C-API a few years back
during a Google Summer of Code, the results are languishing on
https://bitbucket.org/waedt/wxpython_cffi.
So thanks for wxPython, and stay tuned, hopefully I can make some
progress here
Matti
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel at python.org
Matplotlib-devel Info Page
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20161019/6b3e5a47/attachment.html>