[Python-Dev] PyPy 1.7 - widening the sweet spot
Amaury Forgeot d'Arc
amauryfa at gmail.com
Tue Nov 22 21:43:22 CET 2011
More information about the Python-Dev mailing list
Tue Nov 22 21:43:22 CET 2011
- Previous message: [Python-Dev] PyPy 1.7 - widening the sweet spot
- Next message: [Python-Dev] PyPy 1.7 - widening the sweet spot
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2011/11/22 Philip Jenvey <pjenvey at underboss.org> > One reason to target 3.2 for now is it's not a moving target. There's > overhead involved in managing modifications to the pure python standard lib > needed for PyPy, tracking 3.3 changes as they happen as well exacerbates > this. > > The plans to split the standard lib into its own repo separate from core > CPython will of course help alternative implementations here. > I don't see how it would help here. Copying the CPython Lib/ directory is not difficult, even though PyPy made slight modifications to the files, and even without any merge tool. OTOH when PyPy changed minor versions (from 2.7.0 to 2.7.2 IIRC) most of the work was to follow the various tiny fixes made to the built-in modules: _io, _ssl and _multiprocessing. -- Amaury Forgeot d'Arc -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20111122/d4a988f7/attachment.html>
- Previous message: [Python-Dev] PyPy 1.7 - widening the sweet spot
- Next message: [Python-Dev] PyPy 1.7 - widening the sweet spot
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list