Re: #! /usr/bin/python{,3} -Es

2012-10-26 Thread Floris Bruynooghe
On 25 October 2012 20:34, Piotr Ożarowski pi...@debian.org wrote: [Steve Langasek, 2012-10-25] On Thu, Oct 25, 2012 at 10:56:05AM -0400, Barry Warsaw wrote: Using -E fixed the immediate bug, but I think it is generally useful to include -s also, so as to avoid any potential breakage of

Re: #! /usr/bin/python{,3} -Es

2012-10-26 Thread Thomas Kluyver
On 26 October 2012 09:19, Floris Bruynooghe f...@devork.be wrote: Several people have said they don't think this is a good idea. But why not? There is a bad effect if you don't rewrite the shebang to /usr/bin/python[3] -ES that we know of, but is there any example of where such a shebang

Re: #! /usr/bin/python{,3} -Es

2012-10-26 Thread Jakub Wilk
* Thomas Kluyver tho...@kluyver.me.uk, 2012-10-26, 11:03: Are there any situations where you might want to run a system script with modified Python environment variables? I can't think of any off the top of my head. Here's the list of environment variables:

Re: #! /usr/bin/python{,3} -Es

2012-10-26 Thread Chow Loong Jin
On 26/10/2012 18:33, Jakub Wilk wrote: * Thomas Kluyver tho...@kluyver.me.uk, 2012-10-26, 11:03: Are there any situations where you might want to run a system script with modified Python environment variables? I can't think of any off the top of my head. Here's the list of environment

Re: #! /usr/bin/python{,3} -Es

2012-10-26 Thread Thomas Kluyver
On 26 October 2012 11:53, Chow Loong Jin hyper...@debian.org wrote: What is the definition of system script? Any script installed via dpkg, perhaps? I wouldn't have said so - I install plenty of Python scripts from packages, like /usr/bin/ipython, that I wouldn't call system scripts. I don't

Re: #! /usr/bin/python{,3} -Es

2012-10-26 Thread Paul Tagliamonte
On Fri, Oct 26, 2012 at 11:03:34AM +0100, Thomas Kluyver wrote: On 26 October 2012 09:19, Floris Bruynooghe f...@devork.be wrote: Several people have said they don't think this is a good idea. But why not? There is a bad effect if you don't rewrite the shebang to /usr/bin/python[3] -ES

Re: #! /usr/bin/python{,3} -Es

2012-10-26 Thread Thomas Kluyver
On 26 October 2012 14:20, Paul Tagliamonte paul...@debian.org wrote: django-admin if I'm using a virtualenv? Perhaps I'm missing the point? Will this just break all virtualenv support? To my mind, django-admin is not a system script. A system script would be something like the

Re: #! /usr/bin/python{,3} -Es

2012-10-26 Thread Floris Bruynooghe
On 26 October 2012 14:20, Paul Tagliamonte paul...@debian.org wrote: On Fri, Oct 26, 2012 at 11:03:34AM +0100, Thomas Kluyver wrote: On 26 October 2012 09:19, Floris Bruynooghe f...@devork.be wrote: Several people have said they don't think this is a good idea. But why not? There is a bad

Re: #! /usr/bin/python{,3} -Es

2012-10-26 Thread Barry Warsaw
On Oct 26, 2012, at 09:19 AM, Floris Bruynooghe wrote: On 25 October 2012 20:34, Piotr Ożarowski pi...@debian.org wrote: [Steve Langasek, 2012-10-25] On Thu, Oct 25, 2012 at 10:56:05AM -0400, Barry Warsaw wrote: Using -E fixed the immediate bug, but I think it is generally useful to include

Re: #! /usr/bin/python{,3} -Es

2012-10-26 Thread Barry Warsaw
On Oct 26, 2012, at 12:33 PM, Jakub Wilk wrote: * Thomas Kluyver tho...@kluyver.me.uk, 2012-10-26, 11:03: Are there any situations where you might want to run a system script with modified Python environment variables? I can't think of any off the top of my head. Here's the list of environment