Re: [PATCH] Standardize python shebangs
- From
James Denholm <nod.helm@gmail.com>
- Date
- May 7, 2014, 12:03 UTC
- Message-ID
- <e5ca17b7-941d-40eb-abf1-2c0b8d79e79d@email.android.com>
- In-Reply-To
- <536a14f9de982_675a167130cb4@nysa.notmuch>
On 7 May 2014 21:11:53 GMT+10:00, Felipe Contreras <felipe.contreras@gmail.com> wrote:
Show 10 quoted lines
>Johan Herland wrote: >> On Wed, May 7, 2014 at 12:03 PM, Felipe Contreras >> <felipe.contreras@gmail.com> 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.
Yeah, but they shouldn't have to. The build process is already non-"sane", let's please not make it more so?
Moving all instances of "env python" to be "env python2", though, that I think is a reasonable solution (if this is even felt to be a problem).
Regards, James Denholm.