Multiple python3x

Bug #1358202 reported by hurie
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
IUS Community Project
Won't Fix
Undecided
Unassigned

Bug Description

It would be great if we can install multiple of same major python version, like installing python3.3 and python3.4.

Currently, installing python3.4 after python3.3 will yield :

[vagrant@vagrant-centos6 ~]$ sudo yum install python34u
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * epel: kartolo.sby.datautama.net.id
 * ius: hkg.mirror.rackspace.com
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package python34u.x86_64 0:3.4.1-2.ius.centos6 will be installed
--> Processing Dependency: python34u-libs(x86-64) = 3.4.1-2.ius.centos6 for package: python34u-3.4.1-2.ius.centos6.x86_64
--> Processing Dependency: libpython3.4m.so.1.0()(64bit) for package: python34u-3.4.1-2.ius.centos6.x86_64
--> Running transaction check
---> Package python34u-libs.x86_64 0:3.4.1-2.ius.centos6 will be installed
--> Processing Conflict: python34u-3.4.1-2.ius.centos6.x86_64 conflicts python33
--> Finished Dependency Resolution
Error: python34u conflicts with python33-3.3.5-2.ius.centos6.x86_64
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

Revision history for this message
Carl George (carl.george) wrote :

Howdy hurie,

Thanks for your feedback on this. Currently, we are explicitly conflicting with other IUS python3 builds [0]. This is because there are several file conflicts between our builds.

/usr/bin/pydoc3
/usr/bin/python3
/usr/share/man/man1/python3.1.gz
/usr/bin/pyvenv

These files are symbolic links to similar files ending in 3.4. Here are our options.

1. Do nothing, and continue to only allow a single version of IUS python3 installed at a time.
2. Remove every conflicting symbolic link, forcing users to use "python3.4" instead of "python3".
3. Same as 2, but only for the previous major versions (python32, python33), and leave the generic symlinks in the latest stable version (currently python34u).
4. Manage the symbolic links via update-alternatives.

The obvious problem with 2 is that many users will expect /usr/bin/python3 to exist, and this change has the potential for breakage. Utilizing update-alternatives is not something we have done before, but we are up for considering it. More investigation is required.

[0] https://github.com/iuscommunity-pkg/python34u/blob/master/SPECS/python34u.spec#L156-159

Revision history for this message
hurie (hurie83) wrote :

I vote for 1 and 4.

Revision history for this message
bharper (bharper) wrote :

We are moving bug/ticket/issue tracking from Launchpad to GitHub[0]. All stale tickets within Launchpad are getting closed. If you would like us to re-evaluate this request, please create an issue in our GitHub wishlist repository[1].

-Ben

[0] https://lists.launchpad.net/ius-community/msg01635.html
[1] https://github.com/iuscommunity/wishlist

Changed in ius:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.