Not surprisingly, people are still attempting to browse and/or checkout Python source from svn.python.org. They could be following out-of-date instructions from somewhere or might be expecting the svn repos are mirroring the hg ones. This causes wasted time and frustration for users and for us following up on issues. Could some text be added to the svn browser pages to at least indicate that the repo is no longer being updated with a link to the hg.python.org browser? I'm not sure what to do about the repos themselves if people attempt to do an svn co. Perhaps that should just be disabled totally for python? -- Ned Deily, nad@acm.org
On 28/06/2011 17:37, Ned Deily wrote:
Not surprisingly, people are still attempting to browse and/or checkout Python source from svn.python.org. They could be following out-of-date instructions from somewhere or might be expecting the svn repos are mirroring the hg ones. This causes wasted time and frustration for users and for us following up on issues.
Could some text be added to the svn browser pages to at least indicate that the repo is no longer being updated with a link to the hg.python.org browser? I'm not sure what to do about the repos themselves if people attempt to do an svn co. Perhaps that should just be disabled totally for python?
For what it's worth we've had a couple of emails about this to webmaster@python.org (in particular because the viewc svn browser breaks on some latin-1 in source files). All the best, Michael Foord -- http://www.voidspace.org.uk/ May you do good and not evil May you find forgiveness for yourself and forgive others May you share freely, never taking more than you give. -- the sqlite blessing http://www.sqlite.org/different.html
Ned Deily <nad <at> acm.org> writes:
Could some text be added to the svn browser pages to at least indicate that the repo is no longer being updated with a link to the hg.python.org browser? I'm not sure what to do about the repos themselves if people attempt to do an svn co. Perhaps that should just be disabled totally for python?
At least some of the stuff in the SVN repo is still needed, AFAICT. I recently did a build of the Python Windows binary installer, and I understand (from the buildbot instructions) that the best source of some of the external dependencies (bz2, Tcl/Tk, openssl etc.) is still the SVN repo. Regards, Vinay Sajip
On Jun 29, 2011, at 01:05 AM, Vinay Sajip wrote:
Ned Deily <nad <at> acm.org> writes:
Could some text be added to the svn browser pages to at least indicate that the repo is no longer being updated with a link to the hg.python.org browser? I'm not sure what to do about the repos themselves if people attempt to do an svn co. Perhaps that should just be disabled totally for python?
At least some of the stuff in the SVN repo is still needed, AFAICT. I recently did a build of the Python Windows binary installer, and I understand (from the buildbot instructions) that the best source of some of the external dependencies (bz2, Tcl/Tk, openssl etc.) is still the SVN repo.
In fact, it's also not entirely true that svn isn't being updated. We're still cutting any 2.5 and 2.6 releases from svn, though we're also porting the changes into hg. -Barry
On Wed, Jun 29, 2011 at 03:05, Vinay Sajip <vinay_sajip@yahoo.co.uk> wrote:
Ned Deily <nad <at> acm.org> writes:
Could some text be added to the svn browser pages to at least indicate that the repo is no longer being updated with a link to the hg.python.org browser? I'm not sure what to do about the repos themselves if people attempt to do an svn co. Perhaps that should just be disabled totally for python?
At least some of the stuff in the SVN repo is still needed, AFAICT. I recently did a build of the Python Windows binary installer, and I understand (from the buildbot instructions) that the best source of some of the external dependencies (bz2, Tcl/Tk, openssl etc.) is still the SVN repo.
SVN is also used to fetch third-party tools to build documentation, such as: sphinx, docutils, jinja, and pygments. These locations are also advertised on http://docs.python.org/py3k/documenting/building.html (that contains outdated info, but that's another story). Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi
In article <BANLkTik4FKv-=704ua0SmdFj4ab4X5UVdQ@mail.gmail.com>, Sandro Tosi <sandro.tosi@gmail.com> wrote:
On Wed, Jun 29, 2011 at 03:05, Vinay Sajip <vinay_sajip@yahoo.co.uk> wrote:
Could some text be added to the svn browser pages to at least indicate that the repo is no longer being updated with a link to the hg.python.org browser? I'm not sure what to do about the repos themselves if people attempt to do an svn co. Perhaps that should just be disabled totally for python? At least some of the stuff in the SVN repo is still needed, AFAICT. I recently did a build of the Python Windows binary installer, and I understand (from
Ned Deily <nad <at> acm.org> writes: the buildbot instructions) that the best source of some of the external dependencies (bz2, Tcl/Tk, openssl etc.) is still the SVN repo.
SVN is also used to fetch third-party tools to build documentation, such as: sphinx, docutils, jinja, and pygments. These locations are also advertised on http://docs.python.org/py3k/documenting/building.html (that contains outdated info, but that's another story).
Yes, by "for python", I meant the active python development "branches" (py3k->default, 3.2, 2.7). -- Ned Deily, nad@acm.org
Could some text be added to the svn browser pages to at least indicate that the repo is no longer being updated with a link to the hg.python.org browser?
Adding some text to only some pages (namely those that have been migrated to mercurial) is difficult - so difficult that I won't have time for it within the next 12 months. Contributions are welcome.
I'm not sure what to do about the repos themselves if people attempt to do an svn co. Perhaps that should just be disabled totally for python?
It would certainly be possible to "svn rm" the trunk directory, if that is any help. Of course, this would also break all URL links into this tree, of which there are still plenty (and they likely won't go away in the years to come). So I would rather check a file into the directory with the name THIS_SUBVERSION_REPOSITORY_HAS_BEEN_MIGRATED_TO_MERCURIAL_DO_NOT_USE_IT_FOR_ANYTHING_BUT_ARCHEOLOGICAL_RESEARCH.txt See also http://python.cvs.sourceforge.net/viewvc/python/python/ http://python.cvs.sourceforge.net/viewvc/python/python/dist/src/ Regards, Martin
On Jun 30, 2011, at 04:17 PM, Éric Araujo wrote:
Adding a THIS_REPOSITORY_HAS_MOVED file to recent branches looks good.
I'm not against adding this to svn, but please be sure these files don't leak into the tarballs should we need to cut another 2.5 or 2.6 release. I think that just means tweaking sandbox/release/release.py. Cheers, -Barry
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/30/2011 10:32 AM, Barry Warsaw wrote:
On Jun 30, 2011, at 04:17 PM, Éric Araujo wrote:
Adding a THIS_REPOSITORY_HAS_MOVED file to recent branches looks good.
I'm not against adding this to svn, but please be sure these files don't leak into the tarballs should we need to cut another 2.5 or 2.6 release. I think that just means tweaking sandbox/release/release.py.
The fact that releases might / will still be made from those branches argues against including the file on them at all: they are in fact the "canonical" repository locations, even if most of the work is done in hg and patched into them. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk4MmO4ACgkQ+gerLs4ltQ7ybwCgqIkXCdYWIdPM9dHFDa658nLe RYkAnRccCcuCjxQvYSn/jseLJU/ZTmcQ =+fEZ -----END PGP SIGNATURE-----
On Fri, Jul 1, 2011 at 1:40 AM, Tres Seaver <tseaver@palladion.com> wrote:
On 06/30/2011 10:32 AM, Barry Warsaw wrote:
I'm not against adding this to svn, but please be sure these files don't leak into the tarballs should we need to cut another 2.5 or 2.6 release. I think that just means tweaking sandbox/release/release.py.
The fact that releases might / will still be made from those branches argues against including the file on them at all: they are in fact the "canonical" repository locations, even if most of the work is done in hg and patched into them.
Indeed, 2.5 and 2.6 should be left alone. +1 on adding such a file to the more recent branches that are handled in hg, though. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
participants (9)
-
"Martin v. Löwis" -
Barry Warsaw -
Michael Foord -
Ned Deily -
Nick Coghlan -
Sandro Tosi -
Tres Seaver -
Vinay Sajip -
Éric Araujo