<div class="gmail_quote">2011/11/22 Philip Jenvey <span dir="ltr"><<a href="mailto:pjenvey@underboss.org">pjenvey@underboss.org</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div id=":599">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.<br>
<br>
The plans to split the standard lib into its own repo separate from core CPython will of course help alternative implementations here.</div></blockquote></div><br>I don't see how it would help here.<div>Copying the CPython Lib/ directory is not difficult, even though PyPy made slight modifications to the files, and even without any merge tool.</div>
<div><br></div><div>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.</div><div><br></div>
<div>-- <br>Amaury Forgeot d'Arc<br>
</div>