This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ronaldoussoren
Recipients pashkasan, rhettinger, ronaldoussoren
Date 2018-10-01.10:01:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1538388071.64.0.545547206417.issue34859@psf.upfronthosting.co.za>
In-reply-to
Content
@pahskazan: It is correct that '\r\n' is not found in those strings, Python source code is always parsed after conversion to "Unix" line endings with "\n" between lines.  This is basicly the same as the "universal newlines" feature of the open function <https://docs.python.org/3/library/functions.html#open>.

The output you get is therefore expected behaviour. See also Raymond's note about how to use str.find() and the other typo in that line.
History
Date User Action Args
2018-10-01 10:01:11ronaldoussorensetrecipients: + ronaldoussoren, rhettinger, pashkasan
2018-10-01 10:01:11ronaldoussorensetmessageid: <1538388071.64.0.545547206417.issue34859@psf.upfronthosting.co.za>
2018-10-01 10:01:11ronaldoussorenlinkissue34859 messages
2018-10-01 10:01:11ronaldoussorencreate