➜

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 christian.heimes
Recipients Lukasa, SamWhited, Socob, asvetlov, berker.peksag, christian.heimes, epicfaace, era, loewis, marten, njs, r.david.murray, socketpair, underrun, wumpus
Date 2019-08-16.21:10:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1565989801.22.0.568398791313.issue17305@roundup.psfhosted.org>
In-reply-to
Content 
There is no consensus yet. Besides https://pypi.org/project/idna/ we could also consider to wrap libidn2 and ship it. Both PyPI idna and libidn2 have potential licensing issues. I don't like the idea to reinvent the wheel and implement our own idna2008 codec. It's not a trivial task.

Once Python has a working idna2008 encoder, we need to address integration into socket, ssl, http, and asyncio module.
History
Date User Action Args
2019-08-16 21:10:01christian.heimessetrecipients: + christian.heimes, loewis, r.david.murray, njs, asvetlov, socketpair, underrun, berker.peksag, era, marten, Lukasa, wumpus, SamWhited, Socob, epicfaace
2019-08-16 21:10:01christian.heimessetmessageid: <1565989801.22.0.568398791313.issue17305@roundup.psfhosted.org>
2019-08-16 21:10:01christian.heimeslinkissue17305 messages
2019-08-16 21:10:00christian.heimescreate