On Fri, Jun 4, 2010 at 22:36, cool-RR <[email protected]> wrote: > It would be pretty cool, since I won't have to confuse users with the > `_py3` thing, but here are 2 problems: > 1. I find it a little dirty that one single package has two different code > bases.
Well, sure, but having two packages is also dirty. :-) It's a matter of taste. > 2. I like having the Python 3 fork as an actual fork, (i.e. separate repo,) > so I can easily merge changes from the main fork. If I keep them next to > each other like this, it will be hard for me to keep them as separate repos > and therefore hard to do merges. Aha, so you use mercurial or? It's hard to do merges between folders there? I'm used to svn, where that wouldn't be a problem. -- Lennart Regebro: http://regebro.wordpress.com/ Python 3 Porting: http://python3porting.com/ +33 661 58 14 64 _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
