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 irmen
Recipients exarkun, irmen, loewis, pitrou, vstinner
Date 2015-01-17.01:50:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1421459410.61.0.767579993028.issue1103213@psf.upfronthosting.co.za>
In-reply-to
Content
I created the patch about 5 years ago and in the meantime a few things have happened:
- I've not touched C for a very long time now
- I've learned that MSG_WAITALL may be unreliable on certain systems, so any implementation of recvall depending on MSG_WAITALL may inexplicably fail on such systems
- I've been using a python implementation of a custom recv loop in Pyro4 for years
- it is unclear that a C implementation will provide a measurable performance benefit because I think most of the time is spent in the network I/O anyway, and the GIL is released when doing a normal recv (I hope?)

In other words, I will never follow up on my original C-based patch from 5 years ago. I do still like the idea of having a reliable recvall in the stdlib instead of having to code a page long one in my own code.
History
Date User Action Args
2015-01-17 01:50:10irmensetrecipients: + irmen, loewis, exarkun, pitrou, vstinner
2015-01-17 01:50:10irmensetmessageid: <1421459410.61.0.767579993028.issue1103213@psf.upfronthosting.co.za>
2015-01-17 01:50:10irmenlinkissue1103213 messages
2015-01-17 01:50:09irmencreate