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 pitrou
Recipients Arfrever, christian.heimes, loewis, pitrou
Date 2013-05-18.16:02:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1368892950.42.0.133906564681.issue17997@psf.upfronthosting.co.za>
In-reply-to
Content
> It's called "internationalized domain name for APPLICATIONS". ;) It's 
> up to the application to interpret the ASCII text as IDNA encoded
> FQDNs. As far as I know DNS, SSL's CNAME and OS interfaces etc. always 
> use ASCII labels. It's an elegant solution. Just the UI part of an
> application needs to understand IDNA. 

The socket module already decodes to/encodes from IDNA in places (e.g. gethostname()). We need a consistent policy in the stdlib; I would like Martin's advice on this.
History
Date User Action Args
2013-05-18 16:02:30pitrousetrecipients: + pitrou, loewis, christian.heimes, Arfrever
2013-05-18 16:02:30pitrousetmessageid: <1368892950.42.0.133906564681.issue17997@psf.upfronthosting.co.za>
2013-05-18 16:02:30pitroulinkissue17997 messages
2013-05-18 16:02:30pitroucreate