[bah. Resending to the list this time.]
On Feb 1, 2008 11:41 PM, Ralf W. Grosse-Kunstleve
PLEASE GIVE THE PYTHON 3 EXECUTABLE A DIFFERENT NAME AND THE SCRIPTS A DIFFERENT EXTENSION.
We're already have half of that: $ python2.1 -V Python 2.1.3+ $ python2.2 -V Python 2.2.3+ $ python2.3 -V Python 2.3.5 $ python2.4 -V Python 2.4.4 $ python2.5 -V Python 2.5.1 They also have often broken python code that depended on one or two small details, and we haven't needed a new extension before. Now it's true that py3k will break much more than before, but I still don't see the need to differentiate based on extension. Installed libraries have the version in the directory name and installed programs should specify a version in their shebang. The *only* issue I see is that, if you run the 2to3 tool on your 2.6-targetted codebase, it needs to output into a different directory so that you can distinguish them. That's so trivial that I question even mentioning it though. -- Adam Olsen, aka Rhamphoryncus