Ran into a similar concept concern while doing some proof of concept work
for my company. The approach that looked the most promising/easiest for a
clean pypy state (both rpython internal and python globals) was to embed
the sandbox controller and have it call out/create a new sandbox for each
unit
Unless I am missunderstanding, isn't pypy 2.2.1 rather old? Have you
tried a more up-to-date version first? (I seem to see current stable
is 2.6.0 and nightly is 2.7.0-alpha0) My memory is that between 2.3
and 2.4 there was some armhf work done, and that between 2.3 and 2.5 a
whole pile of stuff wa
Agreed, have been doing basically that for some internal code, as the
docs kind of hint:
http://pypy.readthedocs.org/en/latest/embedding.html#more-complete-example
Basically call the pypy_execute_source_ptr() once, passing in a API
struct to fill out for low-level call-backs. (And passing in at t
Looking at rewriting a number of my older python2 scripts to python3
and was hoping in the mean time to also make all of them play nice
with PyPy where possible. However a number of them use pyqt when I
needed a GUI. From what I can find QT still does not play nice with
PyPy yet, however are there
on, but I don't think anyone
>>> got pyqt running on PyPy. Cffi is one option with pymetabiosis being
>>> the other one worth considering. Also I have a bit no clue how much
>>> CPython C extensions your bindings/qt uses, but we have an emulation
>>> layer f
For the compatibility wiki, if nothing major changes this week I feel
fine doing a large pass through it to try and update it. So long as
you don't mind me in the meanwhile on IRC asking silly questions about
some of them. I long ago found it to be a useful resource, and it
still places high on sea
