Why not add a requirement to the PEP such that if a DVCS is chosen then a read-only SVN mirror or gateway should be maintained? Would that be a reasonable compromise?
I have more or less the same opinion as Guido regarding svn merge. It sucks. We bump up against problems with svn merge tracking on a regular basis at work. We'd have switched to a DVCS by now if it wasn't for tool support (trac mostly) and the fact that we use a lot of svn:externals in our repository. On Sat, Feb 28, 2009 at 1:16 AM, Fredrik Lundh <fred...@pythonware.com> wrote: > Btw, one of my concerns is that a move away from Svn breaks the process for > people who pull sources from Svn to build their own Pythons. I know a few > teams that do that, and switching to another system isn't just an apt-get > away for them. Do we have enough log info to be able to determine how common > it is that people pull down source kits using Svn? > > </F> > > On Feb 28, 2009 1:11 AM, <jnol...@gmail.com> wrote: > > The survey isn't biased. You have a value "the same /worse than the status > quo" - wherein the status quo is subversion. If you hate DVCes, you mark it > as "same/worse than the status quo" and we move on. > > No one is suggesting we accept *less* functionality than subversion: in fact > we're looking at these for *more* functionality. > > On Feb 27, 2009 7:04pm, Fredrik Lundh <fred...@pythonware.com> wrote: > > No > need for a long answe... > >> On Feb 27, 2009 9:24 PM, "Brett Cannon" br...@python.org> wrote: > > I had >> a long reply all writt... > > _______________________________________________ > python-committers mailing list > python-committers@python.org > http://mail.python.org/mailman/listinfo/python-committers > > _______________________________________________ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
