[Python-Dev] Looking for VCS usage scenarios

Brett Cannon brett at python.org
Mon Nov 3 23:03:27 CET 2008


On Mon, Nov 3, 2008 at 11:57, Gustavo Niemeyer <gustavo at niemeyer.net> 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 me as an odd
> approach to the selection of scenarios for a tool whose intention is
> precisely to support new usage scenarios.
>
>> As I mentioned in the doc, the first example allows for whatever the
>> DVCS does for diffs, whether that is a full-on branch or not.
>
> Are you looking for new scenarios or for the validation of your document? :-)
>

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
seems whizbang cool but in real life is never used; premature
optimization and all that.

> I'm talking about history-carrying diffs which can be attached and
> sent via mail, not about viewing plain diffs, which every VCS tool in
> the world can do since version 0.0.
>

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 feature.

As for the "via mail" feature, I use Gmail so it doesn't mean anything to me. =)

> Anyway, I guess you already have what you want.  Good luck picking the
> right choice!

Oh, there won't be a right choice (except in my mind), there will just
be the best choice that could be made based on the circumstances.
Working on the issue tracker taught me that lesson.

-Brett


More information about the Python-Dev mailing list