Closed DimitriPapadopoulos closed 1 week ago
This is not really valid, since you can use installer as library and make it install a wheel into Python 2 environment (in which case, IIRC, the coding info is needed).
If Python 2 target environments are supported, then yes, it's best to keep this as is for non-ASCII module and function names.
I may be mistaken, but I cannot find details about support for Python 2 environments in the documentation.
There might not be a mention of that in the docs. No matter that, I would leave the coding comment in place. It doesn't hurt us to keep it there.
As far as I know, only Python 3 is supported. Therefore, get rid of
coding: utf-8
in generated scripts, as UTF-8 is the default.Also, it could be that
module
orimport_name
are not ASCII, but then I would rather add tests with non-ASCII module and function names.