Re: Python Goes Mercurial

Python and Git should get along great. -- http://mail.python.org/mailman/listinfo/python-list

RE: Python Goes Mercurial

Sorry - it's early and I didn't force Outlook to not top-post. Unfortunately, I get asked to top-post here at work ... Tim Delaney -- http://mail.python.org/mailman/listinfo/python-list

RE: Python Goes Mercurial

hursday, 2 April 2009 11:19 PM To: python-list@python.org Subject: Re: Python Goes Mercurial The one thing that makes me want to use git more than any other dvcs is that you don't have to create a new directory for branches. This may be possible in other dvcs's , but git is the only one I&#

Re: Python Goes Mercurial

>> If Martin - which is well above the average programmer - says that he >> would need help with Git, I take this as meaning that most people >> would get lost with Git. Lawrence> I don't feel lost with Git. Does that make me an above-average Lawrence> programmer? No, perhaps

Re: Python Goes Mercurial

In message <5f1038cd-b2c7-420d- bf6e-5872d556f...@u8g2000yqn.googlegroups.com>, Michele Simionato wrote: > The relevance for me is that at work we use Subversion, > but now that Python uses mercurial I am sure there will > be coworkers wanting to switch to Mercurial and I would > like to understan

Re: Python Goes Mercurial

-On [20090405 11:15], Ben Finney (ben+pyt...@benfinney.id.au) wrote: >If you can look at the process that was followed in this decision and >see “push one solution over all others without regard to what the >current situation demands” you're not looking very hard. I did not argue the decision for

Re: Python Goes Mercurial

Jeroen Ruigrok van der Werven writes: > -On [20090405 09:35], Lawrence D'Oliveiro (l...@geek-central.gen.new_zealand) > wrote: > >Tell you what, keep the ad-hominem bullshit out of this discussion, > >and I agree to do the same. Deal? > > I guess I touched a nerve, so you must consider yourself

Re: Python Goes Mercurial

On Sun, Apr 5, 2009 at 3:48 PM, Jeroen Ruigrok van der Werven wrote: > -On [20090405 06:05], Michele Simionato (michele.simion...@gmail.com) wrote: >>P.S. the thing I do not understand if why we are moving >>away from Subversion. Will all the new features entered >>in 1.5 and 1.6 Subversion is now

Re: Python Goes Mercurial

-On [20090405 09:35], Lawrence D'Oliveiro (l...@geek-central.gen.new_zealand) wrote: >Most of the people using Subversion seem to be corporates with a >centralized, top-down-controlled policy for development. Not just corporations. An open source or other type of organisation might just as well

Re: Python Goes Mercurial

On Apr 5, 8:50 am, Lawrence D'Oliveiro wrote: > Michele wrote: > > the thing I do not understand if why we are moving > > away from Subversion. > > Because it's still centralized. That means different developers cannot pursue > parallel branches on their own, those branches must be represented on

Re: Python Goes Mercurial

In message , Jeroen Ruigrok van der Werven wrote: > There's situations where a centralised system like SVN works and there's > situations where a DVCS works better. Most of the people using Subversion seem to be corporates with a centralized, top-down-controlled policy for development. Conway'

Re: Python Goes Mercurial

In message <262497db-d2fd-4217-978c- fc5571f10...@c11g2000yqj.googlegroups.com>, Michele Simionato wrote: > If Martin - which is well above the average programmer - > says that he would need help with Git, I take this as > meaning that most people would get lost with Git. I don't feel lost with G

Re: Python Goes Mercurial

-On [20090405 06:05], Michele Simionato (michele.simion...@gmail.com) wrote: >P.S. the thing I do not understand if why we are moving >away from Subversion. Will all the new features entered >in 1.5 and 1.6 Subversion is now not so bad as it used to >be and it has the advantage of being already the

Re: Python Goes Mercurial

On Apr 5, 5:49 am, Lawrence D'Oliveiro wrote: > Everybody needs help sometime. If you're accustomed to centralized version > control (CVS and SVN), it probably takes some time to get used to the way > distributed systems work. It's nothing to be ashamed of. If Martin - which is well above the av

Re: Python Goes Mercurial

In message <49d80a4a$0$30643$9b622...@news.freenet.de>, "Martin v. Löwis" wrote: >In message , Lawrence D'Oliveiro wrote: > >> Post an example of what you were trying to do, with the exact messages, >> and we can walk you through it. > > Unfortunately, these are many months ago, and I don't reca

Re: Python Goes Mercurial

Martin> I wasn't really asking for help, merely pointing out that I Martin> dislike git because it makes me ask for help (something I did Martin> not have to do for CVS or subversion, except for very special Martin> cases). In fact, Martin is generally the guy answering the CVS an

Re: Python Goes Mercurial

>> I don't like git because it is too difficult for me. In many cases, >> git would refuse to do operations like updating or local committing, >> producing error messages I was not able to understand ... > > Post an example of what you were trying to do, with the exact messages, and > we can walk

Re: Python Goes Mercurial

>> I don't like git because it is too difficult for me. In many cases, >> git would refuse to do operations like updating or local committing, >> producing error messages I was not able to understand ... > > Post an example of what you were trying to do, with the exact messages, and > we can walk

Re: Python Goes Mercurial

Lawrence D'Oliveiro writes: > In message <49d65b62$0$30904$9b622...@news.freenet.de>, "Martin v. Löwis" > wrote: > > > I don't like git because it is too difficult for me. In many > > cases, git would refuse to do operations like updating or local > > committing, producing error messages I was

Re: Python Goes Mercurial

In message <49d65b62$0$30904$9b622...@news.freenet.de>, "Martin v. Löwis" wrote: > I don't like git because it is too difficult for me. In many cases, > git would refuse to do operations like updating or local committing, > producing error messages I was not able to understand ... Post an exampl

Re: Python Goes Mercurial

So what were these "strong antipathies" towards Git, exactly? >>> i haven't read the article you link to, but compared to what i've read >>> on >>> dev "strong antipathies" sounds a bit over-hyped. >> That was the phrase used by GvR. > > well if you find any, please do report back. I don't l

Re: Python Goes Mercurial

2009/4/3 Jeremiah Dodds : > > > On Thu, Apr 2, 2009 at 9:02 PM, andrew cooke wrote: >> >> Echo wrote: >> > 2009/4/2 Jeremiah Dodds >> > >> >> The one thing that makes me want to use git more than any other dvcs is >> >> that you don't have to create a new directory for branches. This may be >> >>

Re: Python Goes Mercurial

On Thu, Apr 2, 2009 at 9:02 PM, andrew cooke wrote: > Echo wrote: > > 2009/4/2 Jeremiah Dodds > > > >> The one thing that makes me want to use git more than any other dvcs is > >> that you don't have to create a new directory for branches. This may be > >> possible in other dvcs's , but git is t

Re: Python Goes Mercurial

> Meh. Use the command line like God intended. I'm sorry to say this Rhodri but there is probably no god ;) The reason I like overlays is that they are data displays that highlight changes without letting me do any action. The VCS works for me before I'm doing any work with it and that's a good

Re: Python Goes Mercurial

On Thu, 02 Apr 2009 19:24:49 +0100, Kay Schluehr wrote: Good to know. Uninstalling a major feature that enhances usability just to make it usable isn't much less ironic though. Meh. Use the command line like God intended. -- Rhodri James *-* Wildebeeste Herder to the Masses -- http://mail

Re: Python Goes Mercurial

Echo wrote: > 2009/4/2 Jeremiah Dodds > >> The one thing that makes me want to use git more than any other dvcs is >> that you don't have to create a new directory for branches. This may be >> possible in other dvcs's , but git is the only one I've seen advertise >> the >> capability. [...] > That

Re: Python Goes Mercurial

2009/4/2 Jeremiah Dodds > The one thing that makes me want to use git more than any other dvcs is > that you don't have to create a new directory for branches. This may be > possible in other dvcs's , but git is the only one I've seen advertise the > capability. > > -- > http://mail.python.org/ma

Re: Python Goes Mercurial

On 2 Apr., 15:05, David Smith wrote: > Kay Schluehr wrote: > > On 1 Apr., 07:56, Lawrence D'Oliveiro > central.gen.new_zealand> wrote: > >> In message <35d429fa-5d13-4703- > > >> a443-6a95c740c...@o6g2000yql.googlegroups.com>, John Yeung wrote: > >>> Here's one that clearly expresses strong antip

Re: Python Goes Mercurial

Kay Schluehr wrote: > On 1 Apr., 07:56, Lawrence D'Oliveiro central.gen.new_zealand> wrote: >> In message <35d429fa-5d13-4703- >> >> a443-6a95c740c...@o6g2000yql.googlegroups.com>, John Yeung wrote: >>> Here's one that clearly expresses strong antipathy: >>> http://mail.python.org/pipermail/pytho

Re: Python Goes Mercurial

On 1 Apr., 07:56, Lawrence D'Oliveiro wrote: > In message <35d429fa-5d13-4703- > > a443-6a95c740c...@o6g2000yql.googlegroups.com>, John Yeung wrote: > > Here's one that clearly expresses strong antipathy: > > > http://mail.python.org/pipermail/python-dev/2009-March/087971.html > > There are lots

Re: Python Goes Mercurial

On Thu, Apr 2, 2009 at 9:12 PM, Paul Boddie wrote: > > "You can do it, but as soon as you go to merge with another repo that > had the unedited commit history, you’ll bump into weirdness (and > probably invalidate your whole reason for rebasing, which was to clean > up the history)." > >  - http:

Re: Python Goes Mercurial

The one thing that makes me want to use git more than any other dvcs is that you don't have to create a new directory for branches. This may be possible in other dvcs's , but git is the only one I've seen advertise the capability. -- http://mail.python.org/mailman/listinfo/python-list

Re: Python Goes Mercurial

On 2 Apr, 04:27, Lawrence D'Oliveiro wrote: > In message <7a1dd0d8-1978-470b- > > a80d-57478d7f7...@q16g2000yqg.googlegroups.com>, Paul Boddie wrote: > > And I've heard stories of "bait and > > switch" with Git: "you can do XYZ with Git but not with ..." followed > > by the discovery that you can'

Re: Python Goes Mercurial

Lawrence D'Oliveiro wrote: > In message , Tim Daneliuk wrote: > >> ,,, when I suggested that better open source tools existed, they kindly >> explained their complete lack of interest in moving several millions >> of lines of code to anything new. > > What was their explanation? > Their entire

Re: Python Goes Mercurial

In message <7a1dd0d8-1978-470b- a80d-57478d7f7...@q16g2000yqg.googlegroups.com>, Paul Boddie wrote: > And I've heard stories of "bait and > switch" with Git: "you can do XYZ with Git but not with ..." followed > by the discovery that you can't realistically do XYZ with Git, either. Cite? -- http

Re: Python Goes Mercurial

In message , Tim Daneliuk wrote: > ,,, when I suggested that better open source tools existed, they kindly > explained their complete lack of interest in moving several millions > of lines of code to anything new. What was their explanation? -- http://mail.python.org/mailman/listinfo/python-list

Re: Python Goes Mercurial

Carl Banks wrote: > On Mar 31, 6:25 pm, Lawrence D'Oliveiro central.gen.new_zealand> wrote: >> >> >> So what were these "strong antipathies" towards Git, exactly? > > Apparently Mercurial had it's own hate club, and the re

Re: Python Goes Mercurial

On 1 Apr, 08:18, Paul Rubin wrote: > Terry Reedy writes: > > > So what were these "strong antipathies" towards Git, exactly? > > > The relevant PEP ishttp://www.python.org/dev/peps/pep-0374/ > > Interesting.  I'm on a project that switched from Mercurial to Git > rec

Re: Python Goes Mercurial

On Mar 31, 6:25 pm, Lawrence D'Oliveiro wrote: > > > So what were these "strong antipathies" towards Git, exactly? Apparently Mercurial had it's own hate club, and the reaction on python-dev was so severe GvR backtracked o

Re: Python Goes Mercurial

On Wed, Apr 1, 2009 at 12:01 AM, Carl Banks wrote: > On Mar 31, 6:25 pm, Lawrence D'Oliveiro central.gen.new_zealand> wrote: >> >> >> So what were these "strong antipathies" towards Git, exactly? > > Apparently Mercurial h

Re: Python Goes Mercurial

Terry Reedy writes: > > So what were these "strong antipathies" towards Git, exactly? > > The relevant PEP is http://www.python.org/dev/peps/pep-0374/ Interesting. I'm on a project that switched from Mercurial to Git recently. I don't have much of a sense of the relevant differences but other

Re: Python Goes Mercurial

In message <35d429fa-5d13-4703- a443-6a95c740c...@o6g2000yql.googlegroups.com>, John Yeung wrote: > Here's one that clearly expresses strong antipathy: > > http://mail.python.org/pipermail/python-dev/2009-March/087971.html There are lots of GUI- and Web-based front ends to Git. And look at on-

Re: Python Goes Mercurial

In message , Terry Reedy wrote: > Lawrence D'Oliveiro wrote: >> >> >> So what were these "strong antipathies" towards Git, exactly? > > The relevant PEP is http://www.python.org/dev/peps/pep

Re: Python Goes Mercurial

Lawrence D'Oliveiro wrote: So what were these "strong antipathies" towards Git, exactly? The relevant PEP is http://www.python.org/dev/peps/pep-0374/ To some Pythonic eyes, the git command

Re: Python Goes Mercurial

Lawrence D'Oliveiro and andrew cooke exchanged: > >>> So what were these "strong antipathies" towards Git, exactly? > > >> compared to what i've read on dev > >> "strong antipathies" sounds a bit over-hyped. > > > That was the phrase used by GvR. > > well if you find any, please do report back. A

Re: Python Goes Mercurial

Lawrence D'Oliveiro wrote: > In message , andrew > cooke wrote: > >> Lawrence D'Oliveiro wrote: >>> mercurial-version-control-system.ars> >>> >>> So what were these "strong antipathies" towards Git, exactly? >> >> i haven't read

Re: Python Goes Mercurial

In message , andrew cooke wrote: > Lawrence D'Oliveiro wrote: >> >> >> So what were these "strong antipathies" towards Git, exactly? > > i haven't read the article you link to, but compared

Re: Python Goes Mercurial

Lawrence D'Oliveiro wrote: > > > So what were these "strong antipathies" towards Git, exactly? you're at the wrong group. there's a lot of interesting discussion in python-dev about this (see

Python Goes Mercurial

So what were these "strong antipathies" towards Git, exactly? -- http://mail.python.org/mailman/listinfo/python-list