[issue21327] socket.type value changes after using settimeout()

R. David Murray report at bugs.python.org
Sat May 2 21:38:35 CEST 2015


R. David Murray added the comment:

The behavior of s.type has changed in 3.5: it now behaves like the proposed new method behaves.  Looking at the source I can't figure out why this is so.  It doesn't seem as though it should be, but this needs to be sorted out before we can proceed.

----------
nosy: +ethan.furman

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue21327>
_______________________________________


More information about the Python-bugs-list mailing list