> > 4. Fix the socket module to loop back on a partial send to send > > the remaining bytes. Pro: no more short writes. Con: what if > > the first few send() calls succeed and then an error is returned? > > Note: code that checks for partial writes will be redundant! > > If you can exempt non-blocking sockets, either 3 or 4 > (preferably 4) is OK. But if you can't exempt non-blocking > sockets, I'll scream bloody murder. It would mean you could > not write high performance socket code in Python (which it > currently is very good for). For one thing, you'd break Medusa. Of course. Don't worry. > > I'm personally in favor of (4), despite the problem with errors > > after the first call. > > The sockets HOWTO already documents the problem. Too > bad I didn't write it before that std lib code got written <wink>. > > I still prefer leaving it alone and telling people to use makefile if > they can't deal with it. I'll vote +0 on 4 if and only if it exempts > nonblocking sockets. Understood. --Guido van Rossum (home page: http://www.pythonlabs.com/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4