[issue32395] asyncio.StreamReader.readuntil is not general enough

Andrew Svetlov added the comment: Agree -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Allow multiple separators in Stream.readuntil ___ Python tracker

[issue32395] asyncio.StreamReader.readuntil is not general enough

Karthikeyan Singaravelan added the comment: I think this is a duplicate of issue37141 where multiple separators are requested for readuntil. I guess we can close one of them as duplicates. -- nosy: +xtreak ___ Python tracker

[issue32395] asyncio.StreamReader.readuntil is not general enough

Change by Anton Patrushev : -- nosy: +socketpair ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue32395] asyncio.StreamReader.readuntil is not general enough

Andrew Svetlov added the comment: Support multiple separators looks easy, I don't expect any performance impact. Like we already have it for strings: s.startswith(('\n', '\r')) Regexps are more expensive thing, callbacks are kind of evil. Let's add a patch for

[issue32395] asyncio.StreamReader.readuntil is not general enough

Change by Yury Selivanov : -- nosy: +asvetlov ___ Python tracker ___ ___

[issue32395] asyncio.StreamReader.readuntil is not general enough

New submission from Bruce Merry : I'd proposed one specific solution in Issue 32052 which asvetlov didn't like, so as requested I'm filing a bug about the problem rather than the solution. The specific case I have is reading a protocol in which either \r or \n can be used to