On 8/16/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote: > > OK, then I'll check it into the py3k branch, and backport it to the trunk. > > This raises another procedural question: are we still merging from the > trunk to the 3k branch, or are they now officially split?
I plan to set up merging again; I still think it's useful. > If we still merge, and assuming that the implementations are > sufficiently similar and live in the same files, it would be better > to commit into the trunk, then merge (or wait for somebody else to > merge), then apply any modifications that the 3k branch needs. Yes. But no biggie for new code if it's done the other way around. -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
