Re: Python (Multi) installation?

["J. Lewis Muir" <jlmuir%imca-cat.org@localhost>]

On 09/16, Thomas Klausner wrote:
> All the python3 packages conflicted until
> 
> revision 1.12
> date: 2017-12-13 13:56:10 +0100;  author: jperkin;  state: Exp;  lines: +2 -1;  commitid: oId3ftm4FnPzmJiA;
> python36: Disable libpython3.so.
> 
> This is a useless library (we've built it incorrectly for a long time so it
> contains no valid symbols) that only creates CONFLICTS with other python3
> packages.  No objection on tech-pkg.  Bump PKGREVISION.

Hijacking this thread, but why is libpython3.so a useless library?  I
can understand it being built incorrectly, but I would think the fix
would be to build it correctly, not disable it.  Wouldn't you want to
link against libpython3.so if you had a program that embeds Python?

On RHEL 7, the python-libs package provides libpython2.7.so.1.0 as shown
in the following (along with some others):

===
$ ls -lF /usr/lib64/libpython2.7.so*
lrwxrwxrwx 1 root root      19 May 24 18:12 /usr/lib64/libpython2.7.so -> libpython2.7.so.1.0*
-rwxr-xr-x 1 root root 1847496 Feb 20  2018 /usr/lib64/libpython2.7.so.1.0*
$ rpm -q -f /usr/lib64/libpython2.7.so.1.0
python-libs-2.7.5-68.el7.x86_64
$ rpm -q -f /usr/lib64/libpython2.7.so
python-devel-2.7.5-68.el7.x86_64
$ rpm -q -f /usr/bin/python2.7
python-2.7.5-68.el7.x86_64
===

Lewis