Hello,

These last three weeks we have been busy working on the cpyext subsystem, which
allows pypy to execute extension modules written with the `Python C API`_.

Today we hacked enough to have wxPython compile, and run its wonderful demo.
This `first screenshot`_ cannot be distinguished from the same run with a
standard python interpreter, but this `second one`_ shows an exception that
CPython never produces.

wxPython is a big extension module: it has more than 500 classes and 7500
functions, most of the code is automatically generated by swig.  It uses
advanced techniques, like "Original Object Return" and cross-platform
polymorphism, that effectively allows the developer to seamlessly subclass C++
objects in Python and write GUI applications efficiently.

The demo application runs reasonably fast, it feels slower than with CPython,
but I did not activate the JIT option of pypy.  It still crashes in some places
(the demo is very comprehensive and covers all the aspects of wxPython), and
threads are expected to not work at the moment.

We had to modify a little the code of wxPython, mainly because it often stores
borrowed references into C++ objects.  This does not work well in pypy, where
all other counted references can disappear, and allows the address of the object
to change.  The solution is to use weak references instead.  The patch is here_,
it will eventually be merged into the upstream wxPython version.

This first real test proves that CPython extensions can be migrated to pypy
without much pain.  It also points some places which can be improved, like
better diagnostics in crashes, better support of distutils...

Amaury Forgeot d'Arc


.. _`Python C API`: http://docs.python.org/c-api
.. _wxPython: http://www.wxpython.org
.. _`first screenshot`: http://imagebin.ca/view/hHtQJ9.html
.. _`second one`: http://imagebin.ca/view/3nPX_sV.html
.. _here: http://codespeak.net/svn/user/afa/wxpython-for-pypy.diff