On Thu, Nov 6, 2008 at 18:31, Steve Holden <[EMAIL PROTECTED]> wrote:
> Brett Cannon wrote:
>> I have started the DVCS PEP which can be seen at
>> http://docs.google.com/Doc?id=dg7fctr4_40dvjkdg64 . Not much is there
>> beyond the rationale, usage scenarios I plan to use, and what other
>> sections
Brett Cannon wrote:
> I have started the DVCS PEP which can be seen at
> http://docs.google.com/Doc?id=dg7fctr4_40dvjkdg64 . Not much is there
> beyond the rationale, usage scenarios I plan to use, and what other
> sections I plan to write.
>
Brett:
Would you care to get a PEP number allocated to
Stephen J. Turnbull wrote:
> In other words, *D*VCS is about keeping and (optionally) communicating
> *local* history, not about reducing the number of VC-related operations
> you do.
The bit I left out where it can get painful is when the patch call to go
back to the first task fails due to chang
Nick Coghlan writes:
> If it isn't already there, suspending work on something to work on
> something else would make a very nice scenario to cover, as it is
> something even the core devs sometimes have to deal with.
>
> I'd expect any DVCS to be able to handily beat what I currently do
>
On Thu, Nov 6, 2008 at 16:47, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Barry Warsaw wrote:
>> On Nov 5, 2008, at 8:36 PM, Stephen J. Turnbull wrote:
>>
>>> You need not feel that way. It's not you---the flexibility of dVCS
>>> means that until the Powers That Be promulgate a Workflow, this will
>
Barry Warsaw wrote:
> On Nov 5, 2008, at 8:36 PM, Stephen J. Turnbull wrote:
>
>> You need not feel that way. It's not you---the flexibility of dVCS
>> means that until the Powers That Be promulgate a Workflow, this will
>> be ambiguous.
>
> You're absolutely right. Adopting a dvcs opens up a m
Tres Seaver schrieb:
> Georg Brandl wrote:
>> Stephen J. Turnbull schrieb:
>>> Tres Seaver writes:
>>>
>>> > svn doesn't have any true tags, AFAIK: everything is a branch.
>>>
>>> Yow! I couldn't have imagined that would be true. And didn't
>
>> It's not exactly true either. svn doesn't ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 6, 2008, at 6:35 AM, Nick Coghlan wrote:
If it isn't already there, suspending work on something to work on
something else would make a very nice scenario to cover, as it is
something even the core devs sometimes have to deal with.
Indeed.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 5, 2008, at 8:36 PM, Stephen J. Turnbull wrote:
You need not feel that way. It's not you---the flexibility of dVCS
means that until the Powers That Be promulgate a Workflow, this will
be ambiguous.
You're absolutely right. Adopting a dvcs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 5, 2008, at 8:36 PM, Stephen J. Turnbull wrote:
I disagree. This doesn't scale to Python size. For distributed VC to
work, somebody has to maintain a repo 24x7. Python has to do this for
the trunk; the additional burden for contributed pat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Georg Brandl wrote:
> Stephen J. Turnbull schrieb:
>> Tres Seaver writes:
>>
>> > svn doesn't have any true tags, AFAIK: everything is a branch.
>>
>> Yow! I couldn't have imagined that would be true. And didn't
>
> It's not exactly true eithe
> > >* Will a DVCS allow simpler operation as if we are still using a
> > > centralized system like CVS or Subversion?
>
> Yes and no. There is nothing to prevent a formal workflow like that
> in CVS/Subversion. However, the separation of "commit" into "record
> && push to authoritativ
On Thu, Nov 6, 2008 at 8:35 PM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
>
> I'd expect any DVCS to be able to handily beat what I currently do with SVN:
Yes, it does. I have extensive experience in bzr, less in git (but
vastly prefer it since I have been using it), and both are relatively
good fo
Stephen J. Turnbull wrote:
> I don't know about svn; I find it pretty painful to use for anything
> but sequential tasking (update ... hack ... commit ... repeat). But
> if you look at http://git.kernel.org/, you'll see a thicket of repos,
> each of which probably contains a few to a few hundred[1
Stephen J. Turnbull schrieb:
> Tres Seaver writes:
>
> > svn doesn't have any true tags, AFAIK: everything is a branch.
>
> Yow! I couldn't have imagined that would be true. And didn't
It's not exactly true either. svn doesn't have either tags or branches,
it has only a single (directory
> > > Unless somebody had committed to the tag - right?
> >
> > That would be insane, right? :)
>
> AFAIK it's not insane, just impossible.
IIRC, I did that for the 2.5.2 tag (or some such), correcting
the spelling of "2st" to "2nd" for the release date.
Regards,
Martin
_
Brett Cannon writes:
> > You need not feel that way. It's not you---the flexibility of dVCS
> > means that until the Powers That Be promulgate a Workflow, this will
> > be ambiguous.
>
> It also took me quite a while to finally grasp exactly how the typical
> workflow could go with a DVCS.
On Wed, Nov 5, 2008 at 17:36, Stephen J. Turnbull <[EMAIL PROTECTED]> wrote:
> In what follows, caveat IANB (I am not Brett, and neither is
> Cosmin), but there is some experience with these systems, and my
> recommendations are based on that.
>
Wow, I'm part of an acronym! That's a first.
> Cosm
Tres Seaver writes:
> svn doesn't have any true tags, AFAIK: everything is a branch.
Yow! I couldn't have imagined that would be true. And didn't
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-d
In what follows, caveat IANB (I am not Brett, and neither is
Cosmin), but there is some experience with these systems, and my
recommendations are based on that.
Cosmin Stejerean writes:
> On Nov 5, 2008, at 12:16 PM, [EMAIL PROTECTED] wrote:
> > What DVCS fits my poor brain best? I feel I'm li
Barry Warsaw writes:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Nov 5, 2008, at 2:44 PM, Martin v. Löwis wrote:
> > Unless somebody had committed to the tag - right?
>
> That would be insane, right? :)
AFAIK it's not insane, just impossible.
Of course in any system you can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin v. Löwis wrote:
>> Yes. My understanding, though I haven't tried it yet, is that newer
>> versions of the bzr-svn plugin do a good job at a full conversion.
>> Basically, every svn branch becomes a bzr branch and all svn tags are
>> converted
2008/11/5 Nick Coghlan <[EMAIL PROTECTED]>:
> Paul Moore wrote:
>> While that would be good, my understanding is that stacked branches in
>> Bazaar only work (for history operations) while you're online. So they
>> make Bazaar work a little like a centralised VCS, I guess. Not sure
>> how that's a
Paul Moore wrote:
> 2008/11/5 Barry Warsaw <[EMAIL PROTECTED]>:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On Nov 5, 2008, at 6:09 AM, Paul Moore wrote:
>>
>>> I'll freely admit a (not very) hidden bias here - the slowness of an
>>> initial clone (or going through the "download a sha
On Wed, Nov 5, 2008 at 12:45, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
>> Before we can make the switch to Bazaar, sure -- if we do.
>
> That is my whole point. Before we switch to whatever DVCS, this
> system should have a complete installation, with all pieces in
> place.
>
> I was just point
On Wed, Nov 5, 2008 at 10:16, <[EMAIL PROTECTED]> wrote:
>
> I apologize that I haven't read whatever Brett's written so far, but I just
> haven't had time, and don't know if there's a PEP yet (and if so, what its
> number is). I did want to get my questions/confusion on the record though.
>
It'
On Wed, Nov 5, 2008 at 07:35, Paul Moore <[EMAIL PROTECTED]> wrote:
> 2008/11/5 David Ripton <[EMAIL PROTECTED]>:
>> All timings very approximate:
>>
>> Time for average user to check out Python sources with bzr: 10 minutes
>>
>> Time for average user to check out Python sources with git or hg: 1 m
On Wed, Nov 5, 2008 at 03:09, Paul Moore <[EMAIL PROTECTED]> wrote:
> 2008/11/3 Brett Cannon <[EMAIL PROTECTED]>:
>> At this point I am looking for any suggestions for fundamental usage
>> scenarios that I am missing from the PEP. If you think the few already
>> listed are missing some core part of
> Before we can make the switch to Bazaar, sure -- if we do.
That is my whole point. Before we switch to whatever DVCS, this
system should have a complete installation, with all pieces in
place.
I was just pointing out that the bazaar installation is not
complete in this respect - I was not askin
On Nov 5, 2008, at 12:16 PM, [EMAIL PROTECTED] wrote:
I apologize that I haven't read whatever Brett's written so far, but
I just
haven't had time, and don't know if there's a PEP yet (and if so,
what its
number is). I did want to get my questions/confusion on the record
though.
What
On Wed, Nov 5, 2008 at 20:15, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > Without a doubt the bazaar branches need a little more loving attention
> > to make them a full working demo, but it's mostly details. The branches
> > *do* contain the whole history, and not just 'select revisions':
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 5, 2008, at 2:44 PM, Martin v. Löwis wrote:
Yes. My understanding, though I haven't tried it yet, is that newer
versions of the bzr-svn plugin do a good job at a full conversion.
Basically, every svn branch becomes a bzr branch and all svn t
> Yes. My understanding, though I haven't tried it yet, is that newer
> versions of the bzr-svn plugin do a good job at a full conversion.
> Basically, every svn branch becomes a bzr branch and all svn tags are
> converted to bzr tags, which are not separate branches, but actual
> symbolic names
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 5, 2008, at 2:15 PM, Martin v. Löwis wrote:
Without a doubt the bazaar branches need a little more loving
attention
to make them a full working demo, but it's mostly details. The
branches
*do* contain the whole history, and not just 'sele
> Without a doubt the bazaar branches need a little more loving attention
> to make them a full working demo, but it's mostly details. The branches
> *do* contain the whole history, and not just 'select revisions':
But there are dozens of branches which aren't represented, plus all the
tags (IIUC)
Paul Moore wrote:
2008/11/5 David Ripton <[EMAIL PROTECTED]>:
All timings very approximate:
Time for average user to check out Python sources with bzr: 10 minutes
Time for average user to check out Python sources with git or hg: 1 minute
Time for average user's trivial patch to be reviewed an
I apologize that I haven't read whatever Brett's written so far, but I just
haven't had time, and don't know if there's a PEP yet (and if so, what its
number is). I did want to get my questions/confusion on the record though.
What DVCS fits my poor brain best? I feel I'm like a dinosaur not bei
David Ripton wrote:
> Time for average user to check out Python sources with bzr: 10 minutes
> Time for average user to check out Python sources with git or hg: 1 minute
> Time for average user's trivial patch to be reviewed and committed: 1 year
> I love DVCS as much as the next guy, but check
2008/11/5 David Ripton <[EMAIL PROTECTED]>:
> All timings very approximate:
>
> Time for average user to check out Python sources with bzr: 10 minutes
>
> Time for average user to check out Python sources with git or hg: 1 minute
>
> Time for average user's trivial patch to be reviewed and committe
2008/11/5 Barry Warsaw <[EMAIL PROTECTED]>:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Nov 5, 2008, at 6:09 AM, Paul Moore wrote:
>
>> I'll freely admit a (not very) hidden bias here - the slowness of an
>> initial clone (or going through the "download a shared repo, unpack
>> it, cre
On Tue, Nov 4, 2008 at 23:19, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> FWIW, I don't consider the current bazaar installation sufficient here.
> It does give a useful insight for those of us unfamiliar with that
> kind of system, and certainly allows those who want to develop with bzr
> alre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 5, 2008, at 6:09 AM, Paul Moore wrote:
I'll freely admit a (not very) hidden bias here - the slowness of an
initial clone (or going through the "download a shared repo, unpack
it, create a branch and update" rigmarole) makes this a nasty test
On 2008.11.05 11:09:24 +, Paul Moore wrote:
> An average user (ie, not a core developer) finds an issue, and has an
> idea how to fix it. He raises a tracker item, checks out the Python
> sources, makes a fix, and wants to upload it to the tracker. Key
> points here are the initial work needed
2008/11/3 Brett Cannon <[EMAIL PROTECTED]>:
> At this point I am looking for any suggestions for fundamental usage
> scenarios that I am missing from the PEP. If you think the few already
> listed are missing some core part of a VCS, please let me know.
My apologies, I can't check if this is alrea
2008/11/5 Stephen J. Turnbull <[EMAIL PROTECTED]>:
> > I see no excuse to let the fact that it's Python make it acceptable
> > to have an application with otherwise unacceptable performance.
>
> Barry and many others obviously find the performance of non-git VCSes
> acceptable. On the other hand
Cosmin Stejerean writes:
> On Tue, Nov 4, 2008 at 12:13 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> > We're Python programmers. We're used to people telling us our
> > tool is too slow. We just say it does the job superbly and it's
> > usually fast enough. :)
> I don't agree with complet
Cosmin Stejerean wrote:
Yes, Python is fast enough most of the time, but when it's not
we put a lot of effort into making it faster. That's why we have a good
collection of modules with C extensions to speed up computationally
intensive applications
So the Pythonic solution is, of course, t
On Tue, Nov 4, 2008 at 13:28, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Ralf Schmitt wrote:
>> On Tue, Nov 4, 2008 at 6:45 PM, Georg Brandl <[EMAIL PROTECTED]> wrote:
>>> Ralf Schmitt schrieb:
I think you really should not exclude any dvcs based on it's
implementation language.
I.e.
> Also, something that should be done for ANY candidate VCS: translate the
> current Python developer FAQ to give the appropriate answers for the
> candidate VCS.
What I would like to see for at least the favored system: provide a demo
installation that is complete in the sense that immediate swit
Ralf Schmitt wrote:
> On Tue, Nov 4, 2008 at 6:45 PM, Georg Brandl <[EMAIL PROTECTED]> wrote:
>> Ralf Schmitt schrieb:
>>> I think you really should not exclude any dvcs based on it's
>>> implementation language.
>>> I.e. requiring it being written in python for the sake of "eating your
>>> own dog
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 4, 2008, at 1:21 PM, Cosmin Stejerean wrote:
I don't agree with completely dismissing performance just because it's
Python. Yes, Python is fast enough most of the time, but when it's
not we
put a lot of effort into making it faster. That's
On Tue, Nov 4, 2008 at 12:13 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Nov 4, 2008, at 1:00 PM, Stephen J. Turnbull wrote:
>
> This is true. Performance is not everything to everyone. Most Bazaar
>> users don't care at all; they say thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 4, 2008, at 1:00 PM, Stephen J. Turnbull wrote:
This is true. Performance is not everything to everyone. Most Bazaar
users don't care at all; they say things like "who cares about a few
seconds in bzr log when it gets the merge right almost
Gustavo Niemeyer writes:
> Both arguments strike me as odd.
I'm an odd fellow, what can I say?
> Having the *option* to leave your history on the server shouldn't
> be a problem, right?
Only if you later try to use it.
> The same goes for (1): having more ways to use the tool isn't
> exac
On Tue, Nov 4, 2008 at 6:45 PM, Georg Brandl <[EMAIL PROTECTED]> wrote:
> Ralf Schmitt schrieb:
>> I think you really should not exclude any dvcs based on it's
>> implementation language.
>> I.e. requiring it being written in python for the sake of "eating your
>> own dogfood" is just a very weak a
Ralf Schmitt schrieb:
> On Mon, Nov 3, 2008 at 1:05 AM, Brett Cannon <[EMAIL PROTECTED]> wrote:
>> I have started the DVCS PEP which can be seen at
>> http://docs.google.com/Doc?id=dg7fctr4_40dvjkdg64 . Not much is there
>> beyond the rationale, usage scenarios I plan to use, and what other
>> sect
2008/11/4 Gustavo Niemeyer <[EMAIL PROTECTED]>:
> How large? Which repositories? Which operations? Which version of Bazaar?
As large as the Python repository. The Python repository (:-)). Local
clone of the repo, when not using a shared repository (I know, "don't
do that" - but it is neverthele
> Trying to expand our buildbot infrastructure to accept patches to test
> out or some patch queue manager might be nice, but I want to be
> realistic with what we have now. That's why I am not worrying about
> this email feature; until I know that we will actually use it and have
> the manpower to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 4, 2008, at 12:21 AM, Stephen J. Turnbull wrote:
(2) New repo formats are added frequently, and taking advantage of new
features often requires upgrading your repo format. So-called
lightweight checkouts can be especially annoying as t
Hello Stephen,
> I haven't used Bazaar beyond "bzr pull" of Mailman once a week or so,
> so I don't dislike it. Things I have observed or have seen discussed
> on the bazaar mailing list that you might want to consider:
> (1) The UI is as baroque as git's, once you consider all the plugins
>a
Brett Cannon wrote:
I have yet to have met anyone who thinks git is great while having
used another DVCS as extensively (and I mean I have never found
someone who has used two DVCSs extensively).
It's entirely possible that there's only room for one
VCS at a time in the average human brain. I
Brett Cannon writes:
> I have yet to have met anyone who thinks git is great while having
> used another DVCS as extensively (and I mean I have never found
> someone who has used two DVCSs extensively).
When XEmacs was considering changing from CVS, I used Darcs as my
primary VCS for about 4 m
On Mon, Nov 3, 2008 at 14:38, Gustavo Niemeyer <[EMAIL PROTECTED]> wrote:
>> Both. First and foremost I am looking for any scenarios people are
>> using now for svn that I didn't cover. After that I can probably add
>> some DVCS-specific things. But the problem with that is my DVCS
>> experience is
On Mon, Nov 3, 2008 at 17:59, Stephen J. Turnbull <[EMAIL PROTECTED]> wrote:
> Jesse Noller writes:
>
> > I don't see how git can be considered given poor windows support -
> > compilation on OS/X can be a bear too.
>
> I can't speak to the "poor Windows support", but I've been compiling
> both i
On Mon, Nov 3, 2008 at 14:58, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Nov 3, 2008, at 5:03 PM, Brett Cannon wrote:
>
>> As I said, one of the scenarios already says patches can be whatever
>> the DVCS supports the best; plain diffs, branches,
Jesse Noller writes:
> I don't see how git can be considered given poor windows support -
> compilation on OS/X can be a bear too.
I can't speak to the "poor Windows support", but I've been compiling
both in MacPorts (pretty much every MacPorts release, which is like
weekly) and from the kernel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 3, 2008, at 5:39 PM, Thomas Wouters wrote:
Here's a real-life Python example: http://bugs.python.org/issue2292. I
actually developed that in two separate branches, one depending on the
other: one branch for *just* the changes to functioncalls
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 3, 2008, at 5:03 PM, Brett Cannon wrote:
As I said, one of the scenarios already says patches can be whatever
the DVCS supports the best; plain diffs, branches, etc. And the
comments for that scenario will point out any perks from that featur
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 3, 2008, at 4:56 PM, Brett Cannon wrote:
But then again, having one scenario that shows svn's weakness directly
wouldn't hurt. I could see a scenario where I start to fix something
in branch A, realize that a deeper issue needs to be fixed, l
> Both. First and foremost I am looking for any scenarios people are
> using now for svn that I didn't cover. After that I can probably add
> some DVCS-specific things. But the problem with that is my DVCS
> experience is limited and thus I don't want to add a scenario that
So try to listen to peo
On Mon, Nov 3, 2008 at 22:56, Brett Cannon <[EMAIL PROTECTED]> wrote:
> But then again, having one scenario that shows svn's weakness directly
> wouldn't hurt. I could see a scenario where I start to fix something
> in branch A, realize that a deeper issue needs to be fixed, leading to
> branch B,
Brett Cannon wrote:
> But then again, having one scenario that shows svn's weakness directly
> wouldn't hurt. I could see a scenario where I start to fix something
> in branch A, realize that a deeper issue needs to be fixed, leading to
> branch B, and then have branch A depend on branch B. Is that
On Mon, Nov 3, 2008 at 11:57, Gustavo Niemeyer <[EMAIL PROTECTED]> wrote:
>> Since I have never seen that come up during Python's development I am
>> going to leave it out. But I do see the benefit and how it might help
>> with future work.
>
> Of course, that's entirely up to you. But it strikes
On Mon, Nov 3, 2008 at 10:35, Thomas Wouters <[EMAIL PROTECTED]> wrote:
>
>
> On Mon, Nov 3, 2008 at 18:57, Brett Cannon <[EMAIL PROTECTED]> wrote:
>>
>> On Sun, Nov 2, 2008 at 17:08, Gustavo Niemeyer <[EMAIL PROTECTED]>
>> wrote:
>> > Hi Brett,
>> >
>> >> At this point I am looking for any suggest
On Mon, Nov 3, 2008 at 10:19, Antoine Pitrou <[EMAIL PROTECTED]> wrote:
> Brett Cannon python.org> writes:
>>
>> At this point I am looking for any suggestions for fundamental usage
>> scenarios that I am missing from the PEP. If you think the few already
>> listed are missing some core part of a
> Since I have never seen that come up during Python's development I am
> going to leave it out. But I do see the benefit and how it might help
> with future work.
Of course, that's entirely up to you. But it strikes me as an odd
approach to the selection of scenarios for a tool whose intention i
2008/11/3 İsmail Dönmez <[EMAIL PROTECTED]>:
> On Mon, Nov 3, 2008 at 20:45, Jesse Noller <[EMAIL PROTECTED]> wrote:
> [...]
>> I don't see how git can be considered given poor windows support -
>> compilation on OS/X can be a bear too.
I would say that strong support of all of Python's key platfo
On Mon, Nov 3, 2008 at 4:43 PM, Benjamin Peterson
<[EMAIL PROTECTED]> wrote:
> On Mon, Nov 3, 2008 at 12:41 PM, Eduardo O. Padoan
> <[EMAIL PROTECTED]> wrote:
>> On Mon, Nov 3, 2008 at 4:34 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
>>> :) But actually more interesting is whether we want to add p
Hi,
On Mon, Nov 3, 2008 at 20:45, Jesse Noller <[EMAIL PROTECTED]> wrote:
[...]
> I don't see how git can be considered given poor windows support -
> compilation on OS/X can be a bear too.
I use git on Linux/Mac/Windows day to day, see
http://code.google.com/p/git-osx-installer/
http://code.goo
On Mon, Nov 3, 2008 at 12:34 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Nov 3, 2008, at 12:58 PM, C. Titus Brown wrote:
>
> -> Sticking with a dvcs implemented in Python makes the best sense,
>> -> especially when you consider the plugin a
On Mon, Nov 3, 2008 at 1:05 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
> On Mon, Nov 3, 2008 at 09:58, C. Titus Brown <[EMAIL PROTECTED]> wrote:
>> -> Sticking with a dvcs implemented in Python makes the best sense,
>> -> especially when you consider the plugin architecture. When we
>> -> selecte
On Mon, Nov 3, 2008 at 12:41 PM, Eduardo O. Padoan
<[EMAIL PROTECTED]> wrote:
> On Mon, Nov 3, 2008 at 4:34 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
>> :) But actually more interesting is whether we want to add plugins that
>> assist Python dev workflow. For example, let's say we wanted to hav
On Mon, Nov 3, 2008 at 4:34 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> :) But actually more interesting is whether we want to add plugins that
> assist Python dev workflow. For example, let's say we wanted to have a
> 'fixes' command that automatically updated the Roundup tracker with the
> br
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 3, 2008, at 1:13 PM, Ralf Schmitt wrote:
I have used mercurial extensively (before having used git) and I think
git is great.
It gives you much more freedom to work with your source code than
mercurial.
Ralf, can you describe what you mea
On Mon, Nov 3, 2008 at 18:57, Brett Cannon <[EMAIL PROTECTED]> wrote:
> On Sun, Nov 2, 2008 at 17:08, Gustavo Niemeyer <[EMAIL PROTECTED]>
> wrote:
> > Hi Brett,
> >
> >> At this point I am looking for any suggestions for fundamental usage
> >> scenarios that I am missing from the PEP. If you thin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 3, 2008, at 12:58 PM, C. Titus Brown wrote:
-> Sticking with a dvcs implemented in Python makes the best sense,
-> especially when you consider the plugin architecture. When we
-> selected a new tracker, we didn't make implementation in Pyth
Brett Cannon python.org> writes:
>
> At this point I am looking for any suggestions for fundamental usage
> scenarios that I am missing from the PEP. If you think the few already
> listed are missing some core part of a VCS, please let me know.
You might want to refine the "patch review" scenari
On Mon, Nov 3, 2008 at 7:05 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
> I have yet to have met anyone who thinks git is great while having
> used another DVCS as extensively (and I mean I have never found
> someone who has used two DVCSs extensively).
I have used mercurial extensively (before ha
On Mon, Nov 03, 2008 at 10:05:15AM -0800, Brett Cannon wrote:
-> I have yet to have met anyone who thinks git is great while having
-> used another DVCS as extensively (and I mean I have never found
-> someone who has used two DVCSs extensively).
git is great! I'm switching to it from darcs for a
On Mon, Nov 3, 2008 at 09:57, Antoine Pitrou <[EMAIL PROTECTED]> wrote:
>
> Hi Brett,
>
> Brett Cannon python.org> writes:
>>
>> I have started the DVCS PEP which can be seen at
>> http://docs.google.com/Doc?id=dg7fctr4_40dvjkdg64 . Not much is there
>> beyond the rationale, usage scenarios I plan
On Mon, Nov 3, 2008 at 09:58, C. Titus Brown <[EMAIL PROTECTED]> wrote:
> -> Sticking with a dvcs implemented in Python makes the best sense,
> -> especially when you consider the plugin architecture. When we
> -> selected a new tracker, we didn't make implementation in Python a
> -> requirement,
On Sun, Nov 2, 2008 at 19:03, Benjamin Peterson
<[EMAIL PROTECTED]> wrote:
> On Sun, Nov 2, 2008 at 6:05 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
>> I have started the DVCS PEP which can be seen at
>> http://docs.google.com/Doc?id=dg7fctr4_40dvjkdg64 . Not much is there
>> beyond the rationale,
Hi Brett,
Brett Cannon python.org> writes:
>
> I have started the DVCS PEP which can be seen at
> http://docs.google.com/Doc?id=dg7fctr4_40dvjkdg64 . Not much is there
> beyond the rationale, usage scenarios I plan to use, and what other
> sections I plan to write.
I'm not sure that's the kind
-> Sticking with a dvcs implemented in Python makes the best sense,
-> especially when you consider the plugin architecture. When we
-> selected a new tracker, we didn't make implementation in Python a
-> requirement, but instead a high hurdle. Meaning, if a tracker wasn't
-> written in P
On Sun, Nov 2, 2008 at 17:08, Gustavo Niemeyer <[EMAIL PROTECTED]> wrote:
> Hi Brett,
>
>> At this point I am looking for any suggestions for fundamental usage
>> scenarios that I am missing from the PEP. If you think the few already
>> listed are missing some core part of a VCS, please let me know
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 3, 2008, at 2:46 AM, Ralf Schmitt wrote:
On Mon, Nov 3, 2008 at 1:05 AM, Brett Cannon <[EMAIL PROTECTED]> wrote:
I have started the DVCS PEP which can be seen at
http://docs.google.com/Doc?id=dg7fctr4_40dvjkdg64 . Not much is there
beyond th
On Mon, 2008-11-03 at 08:46 +0100, Ralf Schmitt wrote:
> On Mon, Nov 3, 2008 at 1:05 AM, Brett Cannon <[EMAIL PROTECTED]> wrote:
> > I have started the DVCS PEP which can be seen at
> > http://docs.google.com/Doc?id=dg7fctr4_40dvjkdg64 . Not much is there
> > beyond the rationale, usage scenarios
On Mon, Nov 3, 2008 at 1:05 AM, Brett Cannon <[EMAIL PROTECTED]> wrote:
> I have started the DVCS PEP which can be seen at
> http://docs.google.com/Doc?id=dg7fctr4_40dvjkdg64 . Not much is there
> beyond the rationale, usage scenarios I plan to use, and what other
> sections I plan to write.
>
I t
On Sun, Nov 2, 2008 at 6:05 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
> I have started the DVCS PEP which can be seen at
> http://docs.google.com/Doc?id=dg7fctr4_40dvjkdg64 . Not much is there
> beyond the rationale, usage scenarios I plan to use, and what other
> sections I plan to write.
>
> At
Hi Brett,
> At this point I am looking for any suggestions for fundamental usage
> scenarios that I am missing from the PEP. If you think the few already
> listed are missing some core part of a VCS, please let me know.
As an initial disclaimer, I use bzr in my daily routine. That said,
I'm send
1 - 100 of 101 matches
Mail list logo
