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 r.david.murray
Recipients marten, r.david.murray
Date 2013-02-27.12:37:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1361968643.25.0.00213999000609.issue17305@psf.upfronthosting.co.za>
In-reply-to
Content
Does this mean the differences are only in the canonicalization of unicode values?  IDNA is a wire protocol, which means that an application can't know if it is being asked to decode an idna1 or idna2 string unless there's something in the protocol that tells it.  But if the differences are only on the encoding side, and an idna1 decoder will "do the right thing" with the idna2 string, then that would be interoperable.  I'll have to read the standard, but I don't have time right now :)

idna is a codec:

>>> b'xn--mller-kva.com'.decode('idna')
'müller.com'

(that's python3, it'll be a unicode string in python2, obviously).
History
Date User Action Args
2013-02-27 12:37:23r.david.murraysetrecipients: + r.david.murray, marten
2013-02-27 12:37:23r.david.murraysetmessageid: <1361968643.25.0.00213999000609.issue17305@psf.upfronthosting.co.za>
2013-02-27 12:37:23r.david.murraylinkissue17305 messages
2013-02-27 12:37:22r.david.murraycreate