> R. David already replied to this, but just to reiterate: tests can always<br>
> get updated, and code that fixes a bug (and leaving a file open can be<br>
> considered a bug) can also go in. It's just stuff like code refactoring,<br>
> speed improvements, etc. that can't go into Python 2.7 at this point.<br>
</div>Thanks for the clarification!<br>
<div class="im"><br>
> If/until the stdlib is made into its own repo, should the various VMs<br>
> consider keeping a common Python 2.7 repo that contains nothing but the<br>
> stdlib (or at least just modifications to those) so they can modify in ways<br>
> that CPython can't accept because of compatibility policy? You could keep it<br>
> on <a href="http://hg.python.org" target="_blank">hg.python.org</a> (or wherever) and then all push to it. This might also be a<br>
> good way to share Python implementations of extension modules for Python 2.7<br>
> instead of everyone maintaining there own for the next few years (although I<br>
> think those modules should go into the stdlib directly for Python 3 as<br>
> well). Basically this could be a test to see if communication and<br>
> collaboration will be high enough among the other VMs to bother with<br>
> breaking out the actual stdlib into its own repo or if it would just be a<br>
> big waste of time.<br>
</div>I'd be up for trying this. I don't think it's easy to fork a<br>
subdirectory of CPython though - right now I just keep an unchanged<br>
copy of the 2.7 LIb in our repo (PyPy does the same, at least the last<br>
time I checked).<br></blockquote><div><br></div><div>Looks like hg doesn't have support yet: <a href="http://stackoverflow.com/questions/920355/how-do-i-clone-a-sub-folder-of-a-repository-in-mercurial">http://stackoverflow.com/questions/920355/how-do-i-clone-a-sub-folder-of-a-repository-in-mercurial</a> .</div>
<div> </div><div>The only sane option I can see then is to keep doing what you and PyPy are doing and keep a copy of the stdlib, but now you all simply share the repo instead of keeping your own copies and possibly use subrepos to pull it into your own hg repos.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
> P.S. Do we need a python-implementations mailing list or something for<br>
> discussing overall VM-related stuff among all VMs instead of always bringing<br>
> this up on python-dev? E.g. I wish I had a place where I could get all the<br>
> VM stakeholders' attention to make sure that importlib as it stands in<br>
> Python 3.3 will skip trying to import Python bytecode properly (or if the<br>
> VMs will simply provide their own setup function and that won't be a worry).<br>
> And I would have no problem with keeping it like python-committers in terms<br>
> of closed subscriptions, open archive in order to keep the noise low.<br>
</div>I think a python-implementations list would be a fantastic idea - I<br>
sometimes miss multi-implementation discussions in python-dev, or at<br>
least come in very late.<br></blockquote><div><br></div><div>If other people agree then I will get Barry to create it. </div></div>