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 loewis
Recipients Justin.Cappos, bbangert, exarkun, giampaolo.rodola, loewis, ned.deily, nicdumz, pitrou, ronaldoussoren, roysmith
Date 2010-11-21.20:49:27
SpamBayes Score 5.7708e-06
Marked as misclassified No
Message-id <4CE985D6.7030408@v.loewis.de>
In-reply-to <1290372035.17.0.457676089087.issue7995@psf.upfronthosting.co.za>
Content
> 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.
History
Date User Action Args
2010-11-21 20:49:28loewissetrecipients: + loewis, ronaldoussoren, exarkun, roysmith, pitrou, giampaolo.rodola, ned.deily, nicdumz, bbangert, Justin.Cappos
2010-11-21 20:49:27loewislinkissue7995 messages
2010-11-21 20:49:27loewiscreate