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 synapse
Recipients docs@python, synapse
Date 2010-10-14.08:42:42
SpamBayes Score 0.008246731
Marked as misclassified No
Message-id <1287045765.45.0.437204596645.issue10099@psf.upfronthosting.co.za>
In-reply-to
Content
socket.fromfd()'s behaviour is somewhat counter-intutive and should contain a note to warn the user that it'll leave the original FD open. This is important if someone forgets to manually close the file descriptor as it might lead to FD leaks (and kernel memory leaks). This is especially the case when there is no python object associated with the FD, so no destruction will take place.

patch applies to this:
http://docs.python.org/py3k/archives/python-3.1.2-docs-html.tar.bz2

The only thing it does is that it adds a note section with the following message: "The original file descriptor will not be closed."

synapse
History
Date User Action Args
2010-10-14 08:42:45synapsesetrecipients: + synapse, docs@python
2010-10-14 08:42:45synapsesetmessageid: <1287045765.45.0.437204596645.issue10099@psf.upfronthosting.co.za>
2010-10-14 08:42:43synapselinkissue10099 messages
2010-10-14 08:42:43synapsecreate