Note that it's okay for the *development* branch to use /usr/bin/env, in fact, it's preferable so that it's easier to develop against alternative Python's. Once deployed though, it must use /usr/bin/python.
-- You received this bug notification because you are a member of Gwibber Bug Heros, which is subscribed to Gwibber. https://bugs.launchpad.net/bugs/988385 Title: /usr/bin/gwibber-accounts has bogus #! line Status in Gwibber: New Status in “gwibber” package in Ubuntu: New Bug description: % head -n 1 /usr/bin/gwibber-accounts #!/usr/bin/env python This is destined to break. It is never a good idea for production code to use /usr/bin/env. Instead, it should use #!/usr/bin/python just like gwibber-service does. To manage notifications about this bug go to: https://bugs.launchpad.net/gwibber/+bug/988385/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~gwibber-bugs Post to : [email protected] Unsubscribe : https://launchpad.net/~gwibber-bugs More help : https://help.launchpad.net/ListHelp
