Martin Panter <[email protected]> added the comment:
Victor opened Issue 32128 with the same complaint. I think I found the
offending article:
>>> server = NNTP_SSL("nntp.aioe.org")
>>> [response, count, first, last, name] = server.group("comp.lang.python")
>>> last
199267
>>> pprint(server.article(199265)[1].lines)
[. . .
b'Date: Fri, 24 Nov 2017 15:44:26 -0800 (PST)',
. . .
b'Message-ID: <[email protected]>',
b'Subject: Re: Python loop and web server (bottle) in the same script
(Posting',
b' On Python-List Prohibited)',
. . .
b'Content-Transfer-Encoding: quoted-printable',
. . .
b'If processing is I/O bound and not CPU bound, then asyncio should work
fine=',
b'.']
The body uses Quoted-printable encoding, and the previous line ends with an
equals sign “=”, meaning a soft line break. So the full stop is on its own
because the encoder didn’t want to fit it on the previous line. This is valid
(albeit quirky) encoding, and not a problem with the NNTP library.
----------
_______________________________________
Python tracker <[email protected]>
<https://bugs.python.org/issue19613>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
