News for hackers. Stuff that matters.
Re:Presentation on the new Python GIL by ajross on Monday January 18, 2010 @01:57PM (#1060569)
It could, but it doesn't and never has. The standard was written to admit a broader set of behavior than real systems actually implement. And in this case, there's absolutely nothing "surprising" to my eyes about a blocking (!) socket blocking on overflow.

Again: there is already a mechanism in place to support non-blocking behavior, and it's not this one.

There are no comments on this comment yet.