>
> However, it has become a de facto standard for all Python code, and in the
> document itself, there is frequent wording akin to "Identifiers used in the
> standard library must be ASCII compatible ...", and even advice for third
> party libraries.
>
> Which I think is acknowledging that PEP 8 is indeed not only about the
> standard library.
>
> So maybe there should be a bit of text about that at the top.
>
This was my thought as I read the original thread yesterday. There are
tools in the wild which base their style recommendations/enforcements on
PEP 8. Heck, there is even a tool in PyPI called "pep8." While 2.x is out
of support, it *is* still used by many organizations. If nothing else, it
would seem to be useful to branch the pep8 repo ("lastpy2" perhaps?) just
before applying Chris's updates. That would allow enterprising folks to
easily fork and reference back to the last point where the PEP 8 text did
mention Python 2.x.
(This no longer applies to me personally, as I have fully gone over to
Python 3, but at my last job there was still plenty of Python 2 code to be
had.)
Just a thought...
Skip
_______________________________________________
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/UJUBBRQWXNGHXRGFO7WFXFL7DHKQQE6T/
Code of Conduct: http://python.org/psf/codeofconduct/
