I currently have python 2.7 and 3.2 installed concurrently. I just tried to install 3.3 as well, but a file conflicts between 3.2 and 3.3. It is libpython3.so.

Given that we go out of our way e.g. with

$(INSTALL_DATA) Misc/python.pc $(DESTDIR)$(LIBPC)/python-$(VERSION).pc

to avoid clashes, what should be done about PY3LIBRARY?

I see that this was introduced in

http://www.python.org/dev/peps/pep-0384/

Would a configure option to make it easy not to install the conflicting file be acceptable?

See issue #11347. (Python ebuilds in Gentoo manually delete libpython3.so.)

Did you use "make altinstall"?

According to Martin on the bug linked to:

« Having the soname be libpython3 is the whole point of the library, it serves no other reason.

It is intentional that there are file collisions with that file, and either the local admin or the distributor must make an explicit choice which libpython3 should be installed; it should be the one that corresponds to /usr/bin/python (if you install it into /usr/lib). »

Should we close this issue as won't fix?

(on the bug Arfrever linked to, sorry)

No, I don't think you should close this, as you haven't explained what it is that you won't do.

I think that a sensible plan is to introduce a configure flag whose effect is to not install the files which cause the conflict. You set the default to always install the conflicting files, so the standard install of python gets to be the PY3LIBRARY. What this buys you, is that then you can also install another version of python 3 concurrently and easily.

I just need to find a round tuit to write it...

To quote the README:

Installing multiple versions
----------------------------
...
For example, if you want to install Python 2.6, 2.7 and 3.4 with 2.7 being the
primary version, you would execute "make install" in your 2.7 build directory
and "make altinstall" in the others.


This makes perfect sense, but now it is impossible to make 3.2 and 3.3 python packages which can be installed simultaneously.

Patrick: it is very difficult to track an issue with shifting focus, since it is never clear what the actual issue is.

Please confirm that it is consensus that
1. It is desired and correct behavior that python3.so is a conflicting file
2. It is possible to avoid the conflict by making "make alt install"

If so, can you please restate what you think the issue is that you want to see resolved?

Why do you say it is impossible to install packages for both python 3.2 and python 3.3? Works perfectly fine for me.

'make altinstall' installs libpython3.so.

Confirming that altinstall installs libpython3.so

Adding 3.2 so I (and other downstream packagers) don't forget to backport the fix.

The discussion here seems to have been abandoned 7 years ago after Martin asked Patrick to clarify the issue. I will close this soon if nobody will explain what is left to be done.