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 gvanrossum
Recipients Anthony.Kong, berker.peksag, catalin.iacob, eric.araujo, gvanrossum, petri.lehtinen, pitrou, poq, python-dev, r.david.murray
Date 2012-02-21.04:18:15
SpamBayes Score 0.005963513
Marked as misclassified No
Message-id <>
Aside: I, too, at first thought this would be a bad idea because it brings back the Python 2 issue of accepting some but not all Unicode strings. But then I realized that by their nature these functions only accepts a very specific set of characters -- so the restriction to (a subset of) ASCII is intrinsic to the functionality, and there is no possibility of confusion. If anything, accepting bytes is more likely to be confusing (they could be EBCDIC! :-). So no objection here. And a slight preference for ValueError.
Date User Action Args
2012-02-21 04:18:16gvanrossumsetrecipients: + gvanrossum, pitrou, eric.araujo, r.david.murray, catalin.iacob, python-dev, petri.lehtinen, poq, Anthony.Kong, berker.peksag
2012-02-21 04:18:16gvanrossumsetmessageid: <>
2012-02-21 04:18:15gvanrossumlinkissue13641 messages
2012-02-21 04:18:15gvanrossumcreate