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 lemburg
Recipients doerwalter, lemburg, mfwitten
Date 2008-10-22.20:04:01
SpamBayes Score 0.0026374087
Marked as misclassified No
Message-id <1224705844.02.0.12923688306.issue4178@psf.upfronthosting.co.za>
In-reply-to
Content
Before CodecInfo tuple subclasses were introduced, the lookup() function
used to return a tuple: (encoder, decoder, stream_reader, stream_writer)

See http://www.python.org/dev/peps/pep-0100/

These were normally addressed by position rather than name and still are
in most cases.

I'm not sure whether the choice of attribute names on CodecInfo was done
on purpose or a simple oversight. Walter added them... I've added him on CC.

They do match the names of the methods on codecs, so perhaps we should
just change everything to read encode/decode instead of encoder/decoder ?!
History
Date User Action Args
2008-10-22 20:04:04lemburgsetrecipients: + lemburg, doerwalter, mfwitten
2008-10-22 20:04:04lemburgsetmessageid: <1224705844.02.0.12923688306.issue4178@psf.upfronthosting.co.za>
2008-10-22 20:04:03lemburglinkissue4178 messages
2008-10-22 20:04:01lemburgcreate