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 possible? > Or is injecting branch dependencies like that not workable? If it > doesn't work, then a branch A/B that a branch C is dependent on would > also work as a scenario (e.g. reworking the testing framework where > you are doing a bunch of different things at once that are culminating > in a single new testing branch that collects everything). > > Those sound like what you are getting after?
Hmm, perhaps your concrete example of this could be a case where someone was working on an object capabilities security model and then realised they needed a more flexible implementation of the import system before their security mechanism was going to work ;) Cheers, Nick. -- Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia --------------------------------------------------------------- _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
