➜

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 r.david.murray
Recipients r.david.murray, sdaoden
Date 2011-04-19.15:45:37
SpamBayes Score 2.1145543e-05
Marked as misclassified No
Message-id <1303227937.84.0.159541070707.issue11867@psf.upfronthosting.co.za>
In-reply-to
Content 
I think the fix is to either put a try/except around the socket shutdown call, or to remove it entirely (I think things will still work right on linux without it).  If you leave the self.c_sock_close = True in, it should take care of the resource warning.
History
Date User Action Args
2011-04-19 15:45:37r.david.murraysetrecipients: + r.david.murray, sdaoden
2011-04-19 15:45:37r.david.murraysetmessageid: <1303227937.84.0.159541070707.issue11867@psf.upfronthosting.co.za>
2011-04-19 15:45:37r.david.murraylinkissue11867 messages
2011-04-19 15:45:37r.david.murraycreate