Martin Panter added the comment:
You can remove the “.. XXX” line; I understand it is just like a TODO comment,
and with this fixed it would no longer be relevant. I suggest putting the links
next to the sentence that ends “. . . the encoding name must be recognized by
Python.”
The links
Martin Panter added the comment:
PEP 263 doesn’t say exactly what encodings are supported. It mentions Shift JIS
is supported, but UTF-16 is not. Only UTF-8 is allowed if the file starts with
a UTF-8 BOM. I guess many of the Python-specific text encodings from the second
section may be
Sameer Kulkarni added the comment:
I have added link to Standard Encodings :
https://docs.python.org/3/library/codecs.html#standard-encodings
and Python Specific Encodings :
https://docs.python.org/3/library/codecs.html#python-specific-encodings
--
keywords: +patch
nosy: +ksameersrk
New submission from Terry J. Reedy:
The source .rst for
https://docs.python.org/3/reference/lexical_analysis.html#encoding-declarations
has at the end:
.. XXX there should be a list of supported encodings.
While I believe this is impractical, there could be a link to
