This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vinay.sajip
Recipients alexis, ceder, eric.araujo, fdrake, guyrozendorn, higery, mhammond, tarek, tim.golden, vinay.sajip
Date 2011-10-24.17:46:39
SpamBayes Score 0.008398419
Marked as misclassified No
Message-id <1319478394.80352.YahooMailNeo@web25808.mail.ukl.yahoo.com>
In-reply-to <1319473568.47.0.365762176827.issue12394@psf.upfronthosting.co.za>
Content
> We’ll have to think about the shebang munging and decide if we keep it.  I think 

> recommending that people use “/usr/bin/env python” (or python3) and not doing 
> anything to the shebang may be the best thing.

What about Windows support? Of course there is PEP 397 which brings shebang-line functionality to Windows, but that PEP has not yet been finalised. Without the existing shebang functionality, IMO there will be problems for Windows users with the “/usr/bin/env python” approach you suggest.
History
Date User Action Args
2011-10-24 17:46:41vinay.sajipsetrecipients: + vinay.sajip, mhammond, fdrake, ceder, tim.golden, tarek, eric.araujo, alexis, higery, guyrozendorn
2011-10-24 17:46:39vinay.sajiplinkissue12394 messages
2011-10-24 17:46:39vinay.sajipcreate