On Wed, May 7, 2014 at 1:11 PM, Felipe Contreras <felipe.contreras@xxxxxxxxx> wrote: > Johan Herland wrote: >> On Wed, May 7, 2014 at 12:03 PM, Felipe Contreras >> <felipe.contreras@xxxxxxxxx> wrote: >> > It's better if all our scripts use the same '/usr/bin/env python'. >> >> Only if they are source compatible with both Python2 and Python3. See >> PEP394 <URL: http://legacy.python.org/dev/peps/pep-0394/ >. Otherwise >> (for python2-only scripts) '/usr/bin/env python2' is the way to go. > > It doesn't matter. People and aistributions have to change them anyway. No, that's _exactly_ what PEP394 addresses. If we standardize on '/usr/bin/env python2' (I assume all our .py scripts are Python2) then they should work on _all_ distros, and Arch Linux would not have to do their current python -> python2 hack (which you referred in another thread). If we instead standardize on '/usr/bin/env python' instead, we only end up annoying forward-looking distros that (want to) enable python == python3 (but obviously also provide python2 for as long as necessary). ...Johan -- Johan Herland, <johan@xxxxxxxxxxx> www.herland.net -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html