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 vstinner
Recipients gvanrossum, socketpair, vstinner, yselivanov
Date 2015-11-27.22:49:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwYknWsgDeLHVcF2+jDf7xd+9oBj79rWyqmuuu9cFN7EcQ@mail.gmail.com>
In-reply-to <1448659598.46.0.288346349625.issue25752@psf.upfronthosting.co.za>
Content
I like the idea. It's common in protocols to have different kinds of
"terminators" to mark the end of a message. C strings use a null byte
for example. I would be trivial to accept other terminators, since we
don't store received bytes as lines, but as a raw byte string
(technically in a bytearray).

> if not isinstance(separator, bytes) or len(separator) != 1:

Yes, we should only reject empty terminator string. But terminator
strings of more than 1 character are fine, no? I don't think that we
need to put an arbitrary limitation here.

> Since I cannot create pull-request, I will write just here what I want:

Oh, what is your problem? You can use https://github.com/python/asyncio
History
Date User Action Args
2015-11-27 22:49:32vstinnersetrecipients: + vstinner, gvanrossum, socketpair, yselivanov
2015-11-27 22:49:32vstinnerlinkissue25752 messages
2015-11-27 22:49:32vstinnercreate