On Sat, 16 Feb 2013 11:12:49 +0100 Antoine Pitrou <solipsis at pitrou.net> wrote: > On Sat, 16 Feb 2013 19:18:22 +1000 > Nick Coghlan <ncoghlan at gmail.com> wrote: > > On Sat, Feb 16, 2013 at 2:21 PM, Daniel Holth <dholth at gmail.com> wrote: > > > #. Python scripts must appear in ``scripts`` and begin with exactly > > > ``b'#!python'`` in order to enjoy script wrapper generation and > > > ``#!python`` rewriting at install time. They may have any or no > > > extension. > > > > For compatibility with file encoding declarations, I believe this > > needs to be relaxed to starting with '#!python' in the source file > > encoding, rather than strictly b'#!python' (which will only be the > > case for ASCII compatible encodings). > > I may be wrong, but I am not aware that Python is able to read encoding > declarations in a non-ASCII compatible encoding :-) > > Also, given the shebang line is for use by the OS, the appropriate > encoding should be decided by the OS, not Python conventions. But I > would surprised if a shebang-compatible used a non-ASCII encoding by > default. I mean non-ASCII compatible. Regards Antoine.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4