Changes by koobs koobs.free...@gmail.com:
--
nosy: +koobs
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17975
___
___
Python-bugs-list mailing
Martin v. Löwis added the comment:
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
Arfrever Frehtes Taifersar Arahesis added the comment:
'make altinstall' installs libpython3.so.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17975
___
koobs added the comment:
Confirming that altinstall installs libpython3.so
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17975
___
___
Patrick Welche added the comment:
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?
--
___
Python tracker rep...@bugs.python.org
Arfrever Frehtes Taifersar Arahesis added the comment:
See issue #11347. (Python ebuilds in Gentoo manually delete libpython3.so.)
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17975
Antoine Pitrou added the comment:
Did you use make altinstall?
--
nosy: +barry, dmalcolm, pitrou
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17975
___
Antoine Pitrou added the comment:
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
Antoine Pitrou added the comment:
(on the bug Arfrever linked to, sorry)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17975
___
___
Patrick Welche added the comment:
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
Patrick Welche added the comment:
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
New submission from Patrick Welche:
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
12 matches
Mail list logo
