[Python-Dev] PEP: Migrating the Python CVS to Subversion (original) (raw)
Aahz aahz at pythoncraft.com
Fri Jul 29 05:17:31 CEST 2005
- Previous message: [Python-Dev] PEP: Migrating the Python CVS to Subversion
- Next message: [Python-Dev] PEP: Migrating the Python CVS to Subversion
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Jul 28, 2005, Barry Warsaw wrote:
On Thu, 2005-07-28 at 22:14, Tim Peters wrote:
Ah, before I forget, "single repository" has worked very well for Zope (which includes top-level Zope2, Zope3, ZODB, ZConfig, zdaemon, ... projects): http://svn.zope.org/ Long URLs don't really get in the way in practice (rarely a need to type one after initial checkout; even "svn switch" is usually just a tail-end cmdline edit starting from a copy+paste of "svn info" output). It depends. In my use of svn, I do a lot of cross-branch merging and repo-side tagging. Those are done with urls and in those cases, long urls can suck. But we may not do a ton of that with the Python project, and besides it might not be important enough to split the directories.
Why can't you write a Python script to generate the URLs? <0.3 wink>
Aahz (aahz at pythoncraft.com) <*> http://www.pythoncraft.com/
The way to build large Python applications is to componentize and loosely-couple the hell out of everything.
- Previous message: [Python-Dev] PEP: Migrating the Python CVS to Subversion
- Next message: [Python-Dev] PEP: Migrating the Python CVS to Subversion
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]