R. David Murray added the comment: Your example does not show a destroyed socket object, so to what are you referring? Python won't recycle an object as garbage until there are no remaining references to it.
If you think that there is information the socket object "knows" that it is throwing away when the socket is closed, you might be correct (I haven't checked the code), but that would be *correct* behavior at this API level and design: since the socket is no longer connected, that information is no longer valid. Please leave the issue closed until you convince us there's a bug :) If you want to propose some sort of enhancement, the correct forum for this level of enhancement would be the python-ideas mailing list. ---------- resolution: wont fix -> not a bug status: pending -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28447> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
