➜

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 barry, christian.heimes, jesstess, macfreek, r.david.murray, sdaoden, torsten.becker, zvyn
Date 2017-06-02.15:12:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1496416323.26.0.254154818212.issue11783@psf.upfronthosting.co.za>
In-reply-to
Content 
We can't replace IDNA-2003 with IDNA-2008 either. Some applications / protocols / TLDs still use IDNA-2003. I see two options, (1) make encoding configurable somehow, (2) drop implicit IDNA encoding/decoding and force applications to perform explicit IDNA.
History
Date User Action Args
2017-06-02 15:12:03christian.heimessetrecipients: + christian.heimes, barry, macfreek, r.david.murray, jesstess, sdaoden, torsten.becker, zvyn
2017-06-02 15:12:03christian.heimessetmessageid: <1496416323.26.0.254154818212.issue11783@psf.upfronthosting.co.za>
2017-06-02 15:12:03christian.heimeslinkissue11783 messages
2017-06-02 15:12:02christian.heimescreate