[issue4178] codecs: Documentation Inconsistency

2008-10-23 Thread Walter Dörwald
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] http://bugs.python.org/issue4178 ___

[issue4178] codecs: Documentation Inconsistency

2008-10-23 Thread Walter Dörwald
Walter Dörwald [EMAIL PROTECTED] added the comment: Fixed in r67005 (trunk) and r67006 (pk3k). -- resolution: - fixed status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue4178 ___

[issue4178] codecs: Documentation Inconsistency

2008-10-22 Thread Michael Witten
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 =

[issue4178] codecs: Documentation Inconsistency

2008-10-22 Thread Marc-Andre Lemburg
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