[Python-Dev] Let's get PEP 380 into Python 3.3 (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Tue Mar 22 13:15:22 CET 2011
- Previous message: [Python-Dev] Let's get PEP 380 into Python 3.3
- Next message: [Python-Dev] Let's get PEP 380 into Python 3.3
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Mar 22, 2011 at 10:06 PM, rndblnch <rndblnch at gmail.com> wrote:
Sorry to have done that, once again, I was not expecting to actually have the rights to cause any side-effect on <http://hg.python.org/>. I guess that it may not be desirable to allow anyone do such server-side clone.
Unmodified clones don't actually take up much space due to the way the filesystem on the server works, and if they don't get updated within a short period of being created (i.e. by someone with commit rights), the server gets rid of them automatically.
Anyone without push rights for hg.python.org may want to fork the mirror the bitbucket folks set up during the PyCon sprints to avoid having to push the whole repository up to a separate hosting site: https://bitbucket.org/mirror/cpython Done here: <https://bitbucket.org/rndblnch/cpython-pep380/> The pep-380 changeset is pushed on top of current tip and is visible here: <https://bitbucket.org/rndblnch/cpython-pep380/changeset/40b19d1933ea>
Cheers, Nick.
-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message: [Python-Dev] Let's get PEP 380 into Python 3.3
- Next message: [Python-Dev] Let's get PEP 380 into Python 3.3
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]