[Python-Dev] Looking for VCS usage scenarios

Barry Warsaw barry at python.org
Tue Nov 4 00:00:43 CET 2008


-----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, to  
> generalize *-
> and **-unpacking in that context, and one branch to add *- and **- 
> unpacking
> in other contexts, which was a much more contentious proposal. The  
> division
> means that the first part can be committed without the second part  
> *without
> any extra effort from anyone*. I wouldn't have to undo changes, I  
> wouldn't
> have to reapply diffs or do a painful manual merge were the first  
> branch to
> be merged into the trunk. It would be completely straightforward and
> effortless.

Great example.  The looms scenario I posted earlier would be perfect  
for this.  I do this all the time with larger feature development.  I  
can have 4 or 5 threads in a typical loom, though I know of people who  
use many more.  It makes developing depending features actually  
manageable.

- -Barry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)

iQCVAwUBSQ+Cm3EjvBPtnXfVAQJkMwQAg3r/JFAOE3RlxbrtPl48QOyjS3PhN7xg
+wOoVz+FgLTkx2187xbSqBjy8K69uC3R3Y/1Foc7OmhUEtTGMfmStwoWdjB3f2zi
BOgYDPcEaDHC5opfDWtbWpYOJzVcfRJJxhAbevHlKeUSX0/bFd39UY58DXgwR9aI
BAjTj4Gt66U=
=nbTw
-----END PGP SIGNATURE-----


More information about the Python-Dev mailing list