/usr/bin/env is a perfectly good solution for *development* branches of packages, but very definitely not for deployed production versions of applications, for exactly the reasons described in this bug report. Meaning: if you are developing a Python application, by all means use /usr/bin/env in your own code, since this will make it easier to test against a variety of Python versions. But packaging should always install the application using the explicit path to the appropriate Python executable. I'm pretty sure distribute and setuptools do this munging automatically.
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-applets in Ubuntu. https://bugs.launchpad.net/bugs/912625 Title: #!/usr/bin/env python breaks Python-based Ubuntu packages in the presence of virtualenvs, local installations To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/912625/+subscriptions -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
