28 May
2013
28 May
'13
3:45 p.m.
On May 25, 2013, at 05:57 PM, Nick Coghlan wrote:
It seems to me the existing recommendation to use ``#!/usr/bin/env python`` instead of referencing a particular binary already covers the general case. The challenge for the distros is that we want a solution that *ignores* user level virtual environments.
Right. My general recommendation is that upstream's (development version) scripts use #! /usr/bin/env, but that distros and possibly even virtualenv/buildout installs, hardcode the #! to a specific interpreter. We've just had way too many problems when a /usr/bin script uses /usr/bin/env and breaks the world. We also recommend using -Es to isolate the environment as much as possible. -Barry