[pypy-dev] cpyext performance
Armin Rigo
arigo at tunes.org
Thu Aug 30 10:28:30 CEST 2012
Hi Stefan,
On Thu, Aug 30, 2012 at 10:06 AM, Stefan Behnel <stefan_ml at behnel.de> wrote:
> This may not even be that hard to do, but it's unlikely that I'll give this
> a try myself. The turn-over times of building PyPy for an hour or so on a
> remote machine (RAM!) for most non-trivial changes are just way too long to
> make friends with the code base. Even waiting for minutes to get an
> interpreted PyPy in a state where it can start building (let alone running)
> Cython extensions is way beyond the seconds in my usual work flow.
This is a blocker, and one that the plan towards CFFI should
completely fix. It's going to be so much more fun to write regular
Python code and try it immediately :-) rather than hack at the
interpreter and have to wait minutes for tests to run or an hour for a
full pypy build.
A bientôt,
Armin.
More information about the pypy-dev
mailing list