In a lot of situations, it's trivial to have some software use python2 and other software use python3. An apache transition is a lot more difficult, because you can't really have half your site served with one apache and the other half served with a different version (on one IP and all on port 80 without a ton of annoying redirection).
Posted Dec 8, 2008 18:16 UTC (Mon) by nevyn (subscriber, #33129)
[Link]
Actually "in a lot of situations" it's trivial to run two different Apache-httpd's ... the problem is all the other situations where it's a giant PITA.
The same is true of python, yes it's possible to run two versions in some situations ... but due to all the other situations Fedora has said "there will be only one". AIUI Debian ship multiple versions of python, but only one version of some (all?) modules ... which doesn't seem that useful. It'll be interesting to see how Debian manage the py3k transition.
Python 3.0 released
Posted Dec 14, 2008 6:08 UTC (Sun) by njs (subscriber, #40338)
[Link]
In Debian, in almost all cases, there is a single package for each library, but at install-time that package detects which versions of python are installed and automatically sets up the library to work with all of them (including running multiple byte-compiles, etc.). This system is called "python-support".