On Thu, Aug 15, 2013 at 10:15 AM, Sascha Peilicke <speilicke@suse.com> wrote:
On 08/15/2013 02:16 PM, Christian Boltz wrote:
Hello,
Am Dienstag, 13. August 2013 schrieb Sascha Peilicke:
the next openSUSE release will have very strong support for Python3 and I've been working a lot on improving parallel installation of Python2 / Python3 modules. In other words, the most important packages (virtualenv, pip, nose, coverage, Sphinx, ...) now use update-alternatives.
Are there plans to make the /usr/bin/python symlink managed with update- alternatives? If yes, this will open an interesting can of worms ;-)
I'm a bit surprised this isn't the case already. When looking at the mess in /usr/bin, I'm close to puking into the next trashcan. Who is supposed to manage all these links by hand?
/usr/bin/python -> python2.7 /usr/bin/python2 -> python2.7 /usr/bin/python2.7 /usr/bin/python2.7-config /usr/bin/python2-config -> python2.7-config /usr/bin/python3 -> python3.3 /usr/bin/python3.3 /usr/bin/python3.3-config -> python3.3m-config /usr/bin/python3.3m /usr/bin/python3.3m-config /usr/bin/python3-config -> python3.3-config /usr/bin/python-config -> python2-config
So I'm gonna fix this ASAP :-)
This is upstream Just configure, make make install will do that from a pristing tarball. In fact, I'm not a big fan of using alternatives. Both versions aren't so easily switchable. I happen to agree with the can of worms thing. We could use update alternatives for nose and other python scripts, but I'm not sure for python itself. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org