[Python-Dev] Looking for VCS usage scenarios

Barry Warsaw barry at python.org
Mon Nov 3 19:34:43 CET 2008

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 Python a
> -> requirement, but instead a high hurdle.  Meaning, if a tracker  
> wasn't
> -> written in Python it had to be way better than those written in  
> Python.
> I worry about the idea of hacking in any way, shape or form, on the
> version control system used to maintain the Python source code.  I  
> place
> VCSes at the compiler- or OS-level of the toolchain, because you have
> the option of fundamentally screwing up the entire project by playing
> with them.
> So from that perspective it's better to keep it *out* of Python to
> remove the temptation to hack :)

:)  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 branch information.  I'd personally much rather write 10  
lines of Python to add such a plugin than any amount of C or Perl, or  
whatever else. :)

> -> As for dvcs, I think git would have to show overwhelming advantage
> -> over bzr or hg to be considered.
> I personally have found git very, very powerful and good, albeit
> difficult to learn.  It is guaranteed to scale (unless Python gets  
> to be
> significantly bigger and more active than Linux, at any rate) and it  
> has
> a large, very technically capable, and supported user community  
> already.
> I think there are reasons why git should be at least strongly
> considered.

Powerful, scalable, active development and user community would  
certainly apply to the Python-based dvcses.

- -Barry

Version: GnuPG v1.4.9 (Darwin)


More information about the Python-Dev mailing list