This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author rixx
Recipients docs@python, ezio.melotti, rixx, vstinner
Date 2020-12-02.09:54:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1606902898.84.0.956500804562.issue42533@roundup.psfhosted.org>
In-reply-to
Content
The documentation for the encodings.idna module contains no indicator that the RFC it supports has been obsoleted by another RFC: https://docs.python.org/3.10/library/codecs.html#module-encodings.idna

I'm sure this is obvious when you know your RFCs, but when just looking at the docs, it's easy to miss. In #msg379674, Marc-Andre suggested to fix the situation by deprecating or updating IDNA support. I'd like to propose to add a warning message in the meantime, pointing out the newer RFC and linking to the idna package on PyPI (if links to PyPI packages are alright in the docs?)
History
Date User Action Args
2020-12-02 09:54:58rixxsetrecipients: + rixx, vstinner, ezio.melotti, docs@python
2020-12-02 09:54:58rixxsetmessageid: <1606902898.84.0.956500804562.issue42533@roundup.psfhosted.org>
2020-12-02 09:54:58rixxlinkissue42533 messages
2020-12-02 09:54:58rixxcreate