➜

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 flox, r.david.murray
Date 2013-05-19.14:25:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1368973558.56.0.855504114696.issue18012@psf.upfronthosting.co.za>
In-reply-to
Content 
Python2 tends to document where unicode *is* supported, rather than where it is not.  And why would a TypeError be incorrect if the unicode type is not supported?

I do not think it likely that this falls into the 'bug' category at this point in the Python2 lifecycle.
History
Date User Action Args
2013-05-19 14:25:58r.david.murraysetrecipients: + r.david.murray, flox
2013-05-19 14:25:58r.david.murraysetmessageid: <1368973558.56.0.855504114696.issue18012@psf.upfronthosting.co.za>
2013-05-19 14:25:58r.david.murraylinkissue18012 messages
2013-05-19 14:25:58r.david.murraycreate