Dirkjan Ochtman <dirkjan <at> ochtman.nl> writes: > > What I personally would consider interesting for the PEP is a (not too > big) section evaluating where other Python-performance efforts are at. > E.g. does it make sense to propose a u-s merge now when, by the time > 3.3 (or whatever) is released, there'll be a very good PyPy that > sports memory usage competitive for embedded development (already does > right now, I think) and a good tracing JIT?
I think PyPy still targets (and is written in) Python 2.5. Given PyPy's history, it also looks quite difficult to know when it will be ready for production (or perhaps I'm too pessimistic). Regards Antoine. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
