Python interpreter should be hard-coded in /usr/bin/pitivi
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pitivi (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Currently (as of 11.04, and I suspect in 11.10), pitivi breaks if you have another Python executable on your PATH, e.g. using virtualenv or a custom-built Python. As per the Debian Python Policy (I can't find a similar document for Ubuntu other than some poorly maintained wiki pages),
> The preferred specification for the Python interpreter is /usr/bin/python or /usr/bin/pythonX.Y. This ensures that a Debian installation of python is used and all dependencies on additional python modules are met.
> Maintainers should not override the Debian Python interpreter using /usr/bin/env python or /usr/bin/env pythonX.Y. This is not advisable as it bypasses Debian's dependency checking and makes the package vulnerable to incomplete local installations of python.
I think this is reasonable, and also supported by the majority of the Python scripts in my /usr/bin directory.
dwf@barricade:~$ lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04
dwf@barricade:~$ apt-cache policy pitivi
pitivi:
Installed: 0.13.5-1ubuntu4
Candidate: 0.13.5-1ubuntu4
Version table:
*** 0.13.5-1ubuntu4 0
500 http://
100 /var/lib/
This affects several packages so I've created a distribution-level bug, #912625.