[issue12446] StreamReader Readlines behavior odd

2012-12-07 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Yes, this is obviously a duplicate of issue8260. -- nosy: +serhiy.storchaka resolution: -> duplicate stage: -> committed/rejected status: open -> closed superseder: -> When I use codecs.open(...) and f.readline() follow up by f.read() return bad re

[issue12446] StreamReader Readlines behavior odd

2011-06-30 Thread STINNER Victor
STINNER Victor added the comment: See also #8260. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue12446] StreamReader Readlines behavior odd

2011-06-29 Thread Amaury Forgeot d'Arc
Changes by Amaury Forgeot d'Arc : -- nosy: +haypo, lemburg ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue12446] StreamReader Readlines behavior odd

2011-06-29 Thread Thomas Barnet-Lamb
Changes by Thomas Barnet-Lamb : -- title: StreamReader Readlines -> StreamReader Readlines behavior odd ___ Python tracker ___ ___ Pyt

[issue12446] StreamReader Readlines

2011-06-29 Thread Thomas Barnet-Lamb
Changes by Thomas Barnet-Lamb : -- type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue12446] StreamReader Readlines

2011-06-29 Thread Thomas Barnet-Lamb
New submission from Thomas Barnet-Lamb : It appears that StreamReader's readlines method behaves in a strange manner if the StreamReader has, in a previous read operation, decoded more characters than the user asked for; this happens when both the chars and size parameters are used, but only i