https://bugzilla.novell.com/show_bug.cgi?id=779424 https://bugzilla.novell.com/show_bug.cgi?id=779424#c1 Jan Matejek changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low Status|NEW |ASSIGNED Summary|python3 should provide |python3 should provide |/usr/bin/env if only |/usr/bin/python if only |python3 is installed |python3 is installed Severity|Normal |Enhancement --- Comment #1 from Jan Matejek 2012-09-10 16:12:27 UTC --- packages with "#!/usr/bin/env <something>" are broken and must be fixed to include path to actual interpreter. (this is because of dependency detection - "/usr/bin/env" is not a meaningful dependency) What would make sense is to make python3 provide "/usr/bin/python" if it's the only python version in the system. But it is probably impossible to achieve that due to how rpm handles file conflicts. What I'm planning to do is turn "python" into a metapackage requiring something like "python-2.7" or "python-3.3", similar to what gcc and friends do. Then we could have a link in /etc/alternatives where you would pick which python version you want to be the default. Still, with what I think you're trying, this would break. You can have two kinds of pythonic apps: 1. those that install themselves in /usr/lib/pythonX.Y/site-packages in that case, you need to require a specific python version anyway, because python other than X.Y won't see the package files 2. those that install somewhere else, and then attempt to support multiple pythons at once. For those, this /etc/alternatives business might actually help, but you won't be able to leverage this capability in a RPM package - there's an autodep generator which makes your package depend on "python(abi) = X.Y" which is the version the package was built with. And as long as you are forcing some python package through dependencies, be it python or python3, you can as well update the shebang lines i'm keeping the bug open as an enhancement with an altered summary and a low priority, because it makes sense as a "future direction", but it's not a bug in the typical sense. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.