Movatterモバイル変換
[0]ホーム
[Python-Dev] PEP: Migrating the Python CVS to Subversion
Fredrik Lundhfredrik at pythonware.com
Wed Aug 10 12:53:28 CEST 2005
Nicholas Bastin wrote:> It's a mature product. I would hope that that would count for> something. I've had enough corrupted subversion repositories that I'm> not crazy about the thought of using it in a production system. I> know I'm not the only person with this experience.compared to Perforce, SVN is extremely fragile. I've used both foryears, and I've never had Perforce repository break down on me. ourSVN repositories are relatively stable these days, but the clients arestill buggy as hell (mostly along the "I don't feel like doing this today,despite the fact that it worked yesterday, and I don't feel like tellingyou what's wrong either" lines. having to nuke workspaces from timeto time gets boring, quickly.)in contrast, Perforce just runs and runs and runs. the clients alwaysdo what you tell them. and server maintenance is trivial; just make surethat the server starts when the host computer boots, and if you haveenough disk, just leave it running. if you're tight on disk space, trimaway some log files now and then. that's it.but despite this, if all you need is a better CVS, I'd say SVN is goodenough for today's python-dev.I'd still think that a more distributed, mail-driven system (built ontop of Mercurial, Bazaar-NG, or some such (*)) would speed upboth development and patch processing, and also make it a lot easierfor "casual contributors" and "drive-by developers" to help developPython, but that's another story.</F>*) being able to ship a fully working Python-powered SCM with thePython source code would be an extra coolness bonus, of course.
More information about the Python-Devmailing list
[8]ページ先頭