Marc-Andre Lemburg writes: > On 26.08.2021 06:07, Christopher Barker wrote:
> > But now a question -- the current text reads: > > > > "Code in the core Python distribution should always use UTF-8" > > "The following policy is prescribed for the standard library > > ... In addition, string literals and comments must also be in > > ASCII." Alex Martelli had a long, well-reasoned post about why Python's "official" language (specifically, identifiers and comments) should be English despite the strong preference for inclusion of our community. As long as that remains true, I think we should stick to ASCII as a lowest common denominator, with an exception for proper names and testing. > With UTF-8 as standard source code encoding, this is no longer > necessary. > > So the second quote can be changed to "In the standard library, non-default > source code encodings should be used only for test purposes ...". +1 > I think the above should be limited to Python code. In C or other > source files you may well still need a source code encoding. True, but PEP 8 only does apply to Python. PEP 7 is the style guide for C. > No need for the stdlib, since UTF-8 is widely accepted by now > and why should people with non-ASCII names not be able to write > their true name ? +1 While I proposed above that the stated policy should be "ASCII except for proper names", I also think "although practicality beats purity". I think such exceptions will be rare enough that "although practicality" can be left implicit. Steve _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/W7JHKRKDFZ5VOYUKJTPGVVGXSERUHQVS/ Code of Conduct: http://python.org/psf/codeofconduct/
