Re: [python-committers] Survey about DVCSs compared to svn

On Thu, Feb 26, 2009 at 08:10, M.-A. Lemburg wrote: > On 2009-02-26 16:36, Antoine Pitrou wrote: > > Le jeudi 26 février 2009 à 16:10 +0100, M.-A. Lemburg a écrit : > >> I didn't know that and was under the impression that those other > >> systems simply hook up to the svn repo via the standard S

Re: [python-committers] Survey about DVCSs compared to svn

On Thu, Feb 26, 2009 at 8:00 AM, Antoine Pitrou wrote: > Le jeudi 26 février 2009 à 10:50 -0500, Richard Tew a écrit : >> If the SVN hosting went away >> and the chosen DVCS solution did not have a good Windows UI (like >> TortoiseSVN), then I would have to make sad faces. > > Perhaps you can try

Re: [python-committers] Survey about DVCSs compared to svn

> Regarding this DVCS survey in general, Stackless Python is hosted in > the svn.python.org repository. As we are a distinct project from > Python itself, I don't really have a stake in a choice which affects > Python and haven't filled the survey in. If the SVN hosting went away > and the chosen

Re: [python-committers] Survey about DVCSs compared to svn

Le jeudi 26 février 2009 à 17:10 +0100, M.-A. Lemburg a écrit : > This is probably a matter of Internet connection bandwidth then. Not really. To give a point of comparison, when I clone (using Mercurial) the Python trunk at http://code.python.org/hg/trunk, it takes 2 minutes 50 seconds. That's fo

Re: [python-committers] Survey about DVCSs compared to svn

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 26, 2009, at 12:10 PM, Martin v. Löwis wrote: That's already the case, for bzr, right? Correct, in that there are native bzr branches on code.python.org, which I am currently trying to improve. Furthermore, there is the option of hosti

Re: [python-committers] Survey about DVCSs compared to svn

>> That's already the case, for bzr, right? > > Correct, in that there are native bzr branches on code.python.org, which > I am currently trying to improve. Furthermore, there is the option of hosting bzr branches on code.python.org, for committers, right? (not sure whether any committer makes ac

Re: [python-committers] Survey about DVCSs compared to svn

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 26, 2009, at 11:10 AM, M.-A. Lemburg wrote: So just to get this right: The Subversion admins on python.org do not have to setup anything special for DVCS mirror sites to hook up to the main Subversion repo. True. If we wanted to host the D

Re: [python-committers] Survey about DVCSs compared to svn

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 26, 2009, at 11:00 AM, Antoine Pitrou wrote: Perhaps you can try TortoiseHG (http://bitbucket.org/tortoisehg/stable/wiki/Home) with one of the mirrors on http://code.python.org/hg and tell us your observations? This would certainly enlighten

Re: [python-committers] Survey about DVCSs compared to svn

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 26, 2009, at 10:10 AM, M.-A. Lemburg wrote: On 2009-02-26 15:50, Antoine Pitrou wrote: Hi, I'm no trying to advocate switching to a DVCS, but really: I think that's a much better approach and one that reduces the load on the python.org re

Re: [python-committers] DVCS and windows line endings.

> And it is even covered in the "minimal setup" section: > http://www.python.org/dev/peps/pep-0374/#hg I think this setup is incomplete: you should also add encode/decode sections to list all file name patterns that should see line conversion. Not sure when to use cleverencode and when to use dumb

Re: [python-committers] Survey about DVCSs compared to svn

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 26, 2009, at 10:04 AM, Antoine Pitrou wrote: Le jeudi 26 février 2009 à 15:54 +0100, Fredrik Lundh a écrit : "that" was referring to "other hosting facilities", not other repositories on the python.org servers: Ok. Sounds like a regression

Re: [python-committers] Survey about DVCSs compared to svn

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 26, 2009, at 9:27 AM, M.-A. Lemburg wrote: It would also permit fans of all discussed DVCS systems to use their favorite tool, provided there are volunteers to do the hosting. There are. I think this approach will also allow Brett to save

Re: [python-committers] DVCS and windows line endings.

> Thoughts? Procedurally, I think there are many open issues. I'm not sure whether they get collected somewhere - so far, I took the position that I'll wait for a final proposal of a specific technology, with a specific demo setup, and then look what is wrong with this setup. Among the issues tha

Re: [python-committers] Survey about DVCSs compared to svn

On 2009-02-26 16:36, Antoine Pitrou wrote: > Le jeudi 26 février 2009 à 16:10 +0100, M.-A. Lemburg a écrit : >> I didn't know that and was under the impression that those other >> systems simply hook up to the svn repo via the standard Subversion >> interfaces. > > They hook up to the svn repo for

Re: [python-committers] Survey about DVCSs compared to svn

Le jeudi 26 février 2009 à 10:50 -0500, Richard Tew a écrit : > If the SVN hosting went away > and the chosen DVCS solution did not have a good Windows UI (like > TortoiseSVN), then I would have to make sad faces. Perhaps you can try TortoiseHG (http://bitbucket.org/tortoisehg/stable/wiki/Home) wi

Re: [python-committers] Survey about DVCSs compared to svn

On Thu, Feb 26, 2009 at 10:36 AM, Antoine Pitrou wrote: >> However, it is often said that branches in DVCS system are so much >> better to work with. Subversion supports these as well, it's just >> that we currently don't make much use of them and that's what I >> wanted to point out. > > Perhaps

Re: [python-committers] Survey about DVCSs compared to svn

Le jeudi 26 février 2009 à 16:10 +0100, M.-A. Lemburg a écrit : > > I didn't know that and was under the impression that those other > systems simply hook up to the svn repo via the standard Subversion > interfaces. They hook up to the svn repo for mirroring purposes, true. But they also have the

Re: [python-committers] Survey about DVCSs compared to svn

On Thu, Feb 26, 2009 at 4:15 PM, Fredrik Lundh wrote: > Better, worse, or equal in what sense? Obviously, *all* of them are > better in certain senses (patch-oriented instead of revision-oriented > approach, higher (?) development velocity to clarify: I meant tool development - especially GIT is

Re: [python-committers] Survey about DVCSs compared to svn

Better, worse, or equal in what sense? Obviously, *all* of them are better in certain senses (patch-oriented instead of revision-oriented approach, higher (?) development velocity, and not to mention the oh-shiny factor). However, it's highly questionable if any of them is better if we take also

Re: [python-committers] Survey about DVCSs compared to svn

On 2009-02-26 15:50, Antoine Pitrou wrote: > Hi, > > I'm no trying to advocate switching to a DVCS, but really: > >> I think that's a much better approach and one that reduces the >> load on the python.org repo sys-admins. > > How does having 4 more-or-less supported VCSes, rather than 1, lighte

Re: [python-committers] Survey about DVCSs compared to svn

Le jeudi 26 février 2009 à 15:54 +0100, Fredrik Lundh a écrit : > "that" was referring to "other hosting facilities", not other > repositories on the python.org servers: Ok. Sounds like a regression, but anyway. ___ python-committers mailing list pytho

Re: [python-committers] Survey about DVCSs compared to svn

On Thu, Feb 26, 2009 at 3:50 PM, Antoine Pitrou wrote: >> BTW: You can avoid the extra checkout of the branch in Subversion >> by first locally copying the trunk checkout to a new dir (using e.g. >> cp -al) and then running a "svn switch" on it. > > That means you only work on one feature at a ti

Re: [python-committers] Survey about DVCSs compared to svn

On Thu, Feb 26, 2009 at 3:50 PM, Antoine Pitrou wrote: > I'm no trying to advocate switching to a DVCS, but really: > >> I think that's a much better approach and one that reduces the >> load on the python.org repo sys-admins. > > How does having 4 more-or-less supported VCSes, rather than 1, lig

Re: [python-committers] Survey about DVCSs compared to svn

Hi, I'm no trying to advocate switching to a DVCS, but really: > I think that's a much better approach and one that reduces the > load on the python.org repo sys-admins. How does having 4 more-or-less supported VCSes, rather than 1, lighten the load on the sysadmins? Even though the DVCSes are

Re: [python-committers] Survey about DVCSs compared to svn

On 2009-02-26 14:25, Barry Warsaw wrote: >> [providing DVCS facilities instead of switching over the main system] > Alternatively, we continue to provide the svn masters and let other > hosting facilities mirror the native branches (con: there will be a > delay) or let people use their -svn bridges

Re: [python-committers] DVCS and windows line endings.

On Feb 25, 2009, at 7:14 PM, Mark Hammond wrote: So I guess the first question is: how much importance do we want to put on that capability? IMO, this is very important. Jim -- Jim Fulton Zope Corporation ___ python-committers mailing list pyt

Re: [python-committers] Survey about DVCSs compared to svn

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 26, 2009, at 6:03 AM, M.-A. Lemburg wrote: Looking at the PEP 374, the DVCSes don't appear to make life easier for common repo tasks (they each require more or less the same number of commands), so the argument for using a DVCS is more abou

Re: [python-committers] Survey about DVCSs compared to svn

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 26, 2009, at 2:54 AM, Martin v. Löwis wrote: Note that not switching from svn on the backend, but still allowing access with bzr, hg, and git is also an option. And there are two subcategories of that: we provide mirrors of svn branches in t

Re: [python-committers] DVCS and windows line endings.

Le jeudi 26 février 2009 à 16:11 +1100, Mark Hammond a écrit : > > And it is even covered in the "minimal setup" section: > > http://www.python.org/dev/peps/pep-0374/#hg > > I can't make the mercurial instructions work; I'm yet to investigate why > though. There's some doc here: http://www.selen

Re: [python-committers] DVCS and windows line endings.

Brett Cannon wrote: > On Wed, Feb 25, 2009 at 21:11, Mark Hammond > wrote: > But my wider point was that there doesn't seem to be a required > level of functionality, or even a blanket statement along the lines > of "native eol support must offer as mu

Re: [python-committers] Survey about DVCSs compared to svn

On 2009-02-26 00:46, Brett Cannon wrote: > On Wed, Feb 25, 2009 at 15:35, Mark Hammond wrote: > >>> There's an option missing in that survey: >>> >>> [ ] I see a need to switch to a DVCS at all. >> To be fair, the survey isn't asking about a switch, just how they compare >> against svn. >> >> But