Martin v. Löwis <mar...@v.loewis.de> added the comment: > However, I hope we can all agree that having the Python socket object > in a different blocking / non-blocking state than the OS socket > descriptor is wrong. This is what needs to be fixed.
Ok, now I see where your misunderstanding is: you simply can't infer from calling .gettimeout() whether the socket is blocking or not. Python does not "think" you can, nor should you. So I don't think anything needs to be fixed in this respect. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue7995> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
