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 ncoghlan
Recipients doerwalter, ezio.melotti, lemburg, ncoghlan, serhiy.storchaka, vstinner
Date 2013-11-19.11:38:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1384861097.76.0.4680084752.issue19619@psf.upfronthosting.co.za>
In-reply-to
Content
Given the time frame, how about we just go with Serhiy's suggestion of a "known non-Unicode codec" internal blacklist for both 3.3 and 3.4?

I still like the idea of exposing codec type maps for introspection, but designing a decent API for that which also handles type preserving codecs is going to take some work, and can't realistically be included in 3.4.

By my count, if we delay the blacklisting until after we do the codec lookup, there's only seven names we need to block:

>>> from codecs import lookup
>>> blacklist = "base64 uu quopri hex bz2 zlib rot13".split()
>>> for name in blacklist:
...     print(lookup(name).name)
... 
base64
uu
quopri
hex
bz2
zlib
rot-13
History
Date User Action Args
2013-11-19 11:38:17ncoghlansetrecipients: + ncoghlan, lemburg, doerwalter, vstinner, ezio.melotti, serhiy.storchaka
2013-11-19 11:38:17ncoghlansetmessageid: <1384861097.76.0.4680084752.issue19619@psf.upfronthosting.co.za>
2013-11-19 11:38:17ncoghlanlinkissue19619 messages
2013-11-19 11:38:17ncoghlancreate