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 bmerry
Recipients asvetlov, bmerry, yselivanov
Date 2019-06-03.09:32:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1559554350.7.0.981137522594.issue37141@roundup.psfhosted.org>
In-reply-to
Content
Text-based protocols sometimes allow a choice of newline separator - I work with one that allows either \r or \n. Unfortunately that doesn't work with StreamReader.readuntil, which only accepts a single separator, so I've had to do some hacky things to obtain lines without having to 

From discussion in issue 32052, it sounded like extending StreamReader.readuntil to support a tuple of separators would be feasible.
History
Date User Action Args
2019-06-03 09:32:31bmerrysetrecipients: + bmerry, asvetlov, yselivanov
2019-06-03 09:32:30bmerrysetmessageid: <1559554350.7.0.981137522594.issue37141@roundup.psfhosted.org>
2019-06-03 09:32:30bmerrylinkissue37141 messages
2019-06-03 09:32:30bmerrycreate