© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
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/
/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-
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:/