Marc-Andre Lemburg <m...@egenix.com> added the comment:
Amaury Forgeot d'Arc wrote:
>
> Amaury Forgeot d'Arc <amaur...@gmail.com> added the comment:
>
> Buffering applies when writing, not when reading a file.
>
> There is indeed a problem in codecs.py: after a readline(), read() will
> return the content of the internal buffer, and not more.
>
> The "size" parameter is a hint, and should not be used to decide whether the
> character buffer is enough to satisfy the read() request.
> Patch is attached, with test.
Agreed.
The patch looks good except the if-line should read:
if chars >= 0 and len(self.charbuffer) >= chars:
...
Thanks,
--
Marc-Andre Lemburg
eGenix.com
________________________________________________________________________
::: Try our new mxODBC.Connect Python Database Interface for free ! ::::
eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
Registered at Amtsgericht Duesseldorf: HRB 46611
http://www.egenix.com/company/contact/
----------
nosy: +lemburg
title: When I use codecs.open(...) and f.readline() follow up by f.read()
return bad result -> When I use codecs.open(...) and f.readline() follow up by
f.read() return bad result
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue8260>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
