On Fri, Jun 4, 2010 at 10:25 PM, Lennart Regebro <[email protected]> wrote:
> I just had an idea, no idea if it's good or not: > > You could try including both the Python 2 and Python 3 source code in > the sdist, but select different ones for install depending on the > Python version. > > I haven't tried this, but I can't come up with a reason it wouldn't > work. If anyone else can, please tell me before Thursday. ;-) > -- > Lennart Regebro 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. 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. (Keep in mind that the main fork contains three packages, `garlicsim`, `garlicsim_lib` and `garlicsim_wx`, and the Python 3 fork contains `garlicsim` and `garlicsim_lib`, so trying to weave them together will be nontrivial.) Sure, I can figure out some scheme to do this, but it will be messy. Ram.
_______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
