Message 144682 - Python tracker

➜

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	loewis
Recipients	belopolsky, doerwalter, ezio.melotti, loewis, pitrou, r.david.murray
Date	2011-09-30.10:20:03
SpamBayes Score	0.0011484384
Marked as misclassified	No
Message-id	<1317378004.88.0.0268767403702.issue3232@psf.upfronthosting.co.za>
In-reply-to

Content
I agree that the codec shouldn't "decode" unicode strings. However, the operation performed is still meaningful: users may type ACE (ascii-compatibly-encoded) DNS names into a user interface, and the application may then represent this as a "proper" Unicode name. So I propose these changes: - remove support for bytes in codec, but only so for 3.3 (it's actually no change in behavior, since it will continue to raise TypeErrors) - add a function decode_idna to the module, for users that wish to un-IDNA string objects.

I agree that the codec shouldn't "decode" unicode strings. However, the operation performed is still meaningful: users may type ACE (ascii-compatibly-encoded) DNS names into a user interface, and the application may then represent this as a "proper" Unicode name.

So I propose these changes:

- remove support for bytes in codec, but only so for 3.3 (it's actually no change in behavior, since it will continue to raise TypeErrors)
- add a function decode_idna to the module, for users that wish to un-IDNA string objects.

History
Date	User	Action	Args
2011-09-30 10:20:05	loewis	set	recipients: + loewis, doerwalter, belopolsky, pitrou, ezio.melotti, r.david.murray
2011-09-30 10:20:04	loewis	set	messageid: <1317378004.88.0.0268767403702.issue3232@psf.upfronthosting.co.za>
2011-09-30 10:20:04	loewis	link	issue3232 messages
2011-09-30 10:20:03	loewis	create