Message 165295 - 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.

In-reply-to
Author	ncoghlan
Recipients	ncoghlan
Date	2012年07月12日.11:04:33
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1342091074.63.0.386956250979.issue15331@psf.upfronthosting.co.za>

Content
In writing a post looking at a potentially different way of handling codec pipelines that is source compatible across both Python 2 and 3, I noticed that the bytes-bytes codec aliases are all missing but are still listed in the documentation as being supported: base64_codec base64, base-64 bz2_codec bz2 hex_codec hex quopri_codec quopri, quoted-printable, quotedprintable uu_codec uu zlib_codec zip, zlib The canonical names (i.e. *_codec) all work as expected, though.

Content

In writing a post looking at a potentially different way of handling codec pipelines that is source compatible across both Python 2 and 3, I noticed that the bytes-bytes codec aliases are all missing but are still listed in the documentation as being supported:
base64_codec 	base64, base-64
bz2_codec 	bz2
hex_codec 	hex
quopri_codec 	quopri, quoted-printable, quotedprintable
uu_codec 	uu
zlib_codec 	zip, zlib
The canonical names (i.e. *_codec) all work as expected, though.

History
Date	User	Action	Args
2012年07月12日 11:04:34	ncoghlan	set	recipients: + ncoghlan
2012年07月12日 11:04:34	ncoghlan	set	messageid: <1342091074.63.0.386956250979.issue15331@psf.upfronthosting.co.za>
2012年07月12日 11:04:34	ncoghlan	link	issue15331 messages
2012年07月12日 11:04:33	ncoghlan	create

homepage