Message 104385 - Python tracker

➜

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	stutzbach
Recipients	ajaksu2, isterika, jbrouwers, perrygreenfield, pitrou, stutzbach
Date	2010-04-28.00:09:27
SpamBayes Score	0.0053794966
Marked as misclassified	No
Message-id	<1272413377.85.0.0220688181286.issue808164@psf.upfronthosting.co.za>
In-reply-to

Content
The purpose of calling .close() in __del__ is to close the socket when the owner is destroyed yet the program is still running. This prevents the socket from staying open if some other part of the program has somehow acquired a reference to it. telnetlib, urllib, and even the socket module itself contain classes that call .close() within __del__ for this purpose. Unfortunately, that can result in ugly error messages when the interpreter is exiting.

The purpose of calling .close() in __del__ is to close the socket when the owner is destroyed yet the program is still running.

This prevents the socket from staying open if some other part of the program has somehow acquired a reference to it.  telnetlib, urllib, and even the socket module itself contain classes that call .close() within __del__ for this purpose.

Unfortunately, that can result in ugly error messages when the interpreter is exiting.

History
Date	User	Action	Args
2010-04-28 00:09:38	stutzbach	set	recipients: + stutzbach, jbrouwers, perrygreenfield, pitrou, ajaksu2, isterika
2010-04-28 00:09:37	stutzbach	set	messageid: <1272413377.85.0.0220688181286.issue808164@psf.upfronthosting.co.za>
2010-04-28 00:09:28	stutzbach	link	issue808164 messages
2010-04-28 00:09:27	stutzbach	create