On Sat, Nov 14, 2015 at 7:15 PM, Chris Angelico wrote:
> Can the py.exe launcher handle a UTF-16 shebang? (I'm pretty sure Unix
> program loaders won't.) That alone might be a reason for strongly
> encouraging ASCII-compat encodings.
The launcher supports shebangs encoded as UTF-8 (default), UTF-
On Sat, Nov 14, 2015 at 7:06 PM, Steve Dower wrote:
> The native encoding on Windows has been UTF-16 since Windows NT. Obviously
> we've survived without Python tokenization support for a long time, but
> every API uses it.
Windows 2000 was the first version to have broad support for UTF-16.
Wind
On 10/21/15, Serhiy Storchaka wrote:
> On 21.10.15 04:25, Gregory P. Smith wrote:
>> https://www.python.org/dev/peps/pep-0008/#names-to-avoid
>>
>> /"Since module names are mapped to file names, and some file systems are
>> case insensitive and truncate long names, it is important that module
>> n
