Samuel Charron added the comment:
This is a known issue, and will be resolved by improving documentation, I'm
closing this bug
Thanks !
--
status: open -> closed
___
Python tracker
<http://bugs.python.org
Samuel Charron added the comment:
It's also at line #14941 for unicode strings if I understand correctly
With 3.4.0:
>>> "a\x85b\x1ec".splitlines()
['a', 'b', 'c']
--
Samuel Charron added the comment:
A consequence of this bug is that r.read() blocks until a timeout occurs since
the content-length header is not interpreted (I think this is related to the
HTTPResponse.__init__ comment)
--
___
Python tracker
Samuel Charron added the comment:
For an example of a serious bug caused by this, see
http://bugs.python.org/issue22233
--
___
Python tracker
<http://bugs.python.org/issue22
New submission from Samuel Charron:
In some cases, the headers from http.client (that uses email.feedparser) splits
headers at wrong separators. The bug is from the use of str.splitlines (in
email.feedparser) that splits on other characters than \r\n as it should. (See
bug http
New submission from Samuel Charron:
According to the documentation, str.splitlines uses the universal newlines to
split lines.
The documentation says it's all about \r, \n, and \r\n
(https://docs.python.org/3.5/glossary.html#term-universal-newlines)
However, it's also splittin
