[issue10344] codecs.readline doesn't care buffering=0

Terry J. Reedy added the comment: Something seems wrong somewhere. First, codecs.open(filename, mode[, encoding[, errors[, buffering]]]) in the doc, should be, to match the code, in the current sytle codecs.open(filename, mode='rb', encoding=None, errors='strict', buffering=1) The other entries

[issue10344] codecs.readline doesn't care buffering=0

Terry J. Reedy added the comment: Please suggest a specific alteration in the codecs.readline doc that we can then discuss. -- assignee: -> d...@python components: +Documentation -Library (Lib) nosy: +d...@python, terry.reedy ___ Python tracker

[issue10344] codecs.readline doesn't care buffering=0

Santiago Piccinini added the comment: Marc-Andre Lemburg wrote: >Regarding the issue itself: I think this is a wrong interpretation of >what the buffering parameter does. File buffering is different >from .readline() buffering (which can be customized on a per-call >basis by specifying a size pa

[issue10344] codecs.readline doesn't care buffering=0

Marc-Andre Lemburg added the comment: Amaury Forgeot d'Arc wrote: > > Amaury Forgeot d'Arc added the comment: > > Antoine, should codecs.open() be removed or simply aliased to open()? Both is not possible: codecs.open() provides a different API than open(). Unlike open(), codecs.open() allow

[issue10344] codecs.readline doesn't care buffering=0

Amaury Forgeot d'Arc added the comment: Antoine, should codecs.open() be removed or simply aliased to open()? -- nosy: +amaury.forgeotdarc, pitrou ___ Python tracker ___ ___

[issue10344] codecs.readline doesn't care buffering=0

New submission from Santiago Piccinini : codecs.readline has an internal buffer of 72 chars so calling codecs.open with buffering=0 doesn't work as expected although buffering is passed to the underlying __builtin__.open call. Example session: Python 3.2a3+ (py3k, Nov 6 2010, 16:17:14) [GCC