Message206508
| Author |
serhiy.storchaka |
| Recipients |
barry, martin.panter, orsenthil, serhiy.storchaka |
| Date |
2013年12月18日.12:25:42 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1387369544.31.0.659595395463.issue19524@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Thank you Martin for clarification. Now I see the problem.
Here is regenerated for Rietveld patch.
Perhaps more safe will be not close socket, but only set the _closed attribute so that it will be closed just after closing SocketIO.
if h.sock:
h.sock._closed = True
h.sock = None
But this is even more tricky.
Yet one approach is to implement __del__() method in the socket.socket class. But this breaks existing tests. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2013年12月18日 12:25:44 | serhiy.storchaka | set | recipients:
+ serhiy.storchaka, barry, orsenthil, martin.panter |
| 2013年12月18日 12:25:44 | serhiy.storchaka | set | messageid: <1387369544.31.0.659595395463.issue19524@psf.upfronthosting.co.za> |
| 2013年12月18日 12:25:44 | serhiy.storchaka | link | issue19524 messages |
| 2013年12月18日 12:25:43 | serhiy.storchaka | create |
|