[issue4178] codecs: Documentation Inconsistency

New submission from Michael Witten <[EMAIL PROTECTED]>: CodecInfo objects are supposed to have 'encoder' and 'decoder' attributes as per http://www.python.org/doc/2.5.2/lib/module-codecs.html (naturally, this applies to 2.5.* as well). However, at least the CodecInfo object for 'string_escape'

[issue4178] codecs: Documentation Inconsistency

Changes by Michael Witten <[EMAIL PROTECTED]>: -- type: -> behavior ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mai

[issue4178] codecs: Documentation Inconsistency

Michael Witten <[EMAIL PROTECTED]> added the comment: Apparently, it might affect all CodecInfo objects: class CodecInfo(tuple): def __new__(cls, encode, decode, streamreader=None, streamwriter=None, incrementalencoder=None, incrementaldecoder=None, name=None): self = tuple

[issue4178] codecs: Documentation Inconsistency

Marc-Andre Lemburg <[EMAIL PROTECTED]> added the comment: 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 rath

[issue4178] codecs: Documentation Inconsistency

Walter Dörwald <[EMAIL PROTECTED]> added the comment: I agree that the documentation should be fixed to read "encode/decode" instead of "encoder/decoder". ___ Python tracker <[EMAIL PROTECTED]> ___

[issue4178] codecs: Documentation Inconsistency

Walter Dörwald <[EMAIL PROTECTED]> added the comment: Fixed in r67005 (trunk) and r67006 (pk3k). -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]>