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 Shane.Hansen
Recipients Shane.Hansen, docs@python, georg.brandl, pitrou
Date 2012-03-14.16:58:17
SpamBayes Score 1.7947334e-05
Marked as misclassified No
Message-id <1331744298.15.0.025379356395.issue14303@psf.upfronthosting.co.za>
In-reply-to
Content
The python docs state that for socket.makefile "The file object references a dup()ped version of the socket file descriptor, so the file object and socket object may be closed or garbage-collected independently."

In fact for socket.py dup() is never called, and no additional files are opened. Instead an object is returned which uses the original socket and does buffering.

For me, this is the desired behaviour, but just thought I'd mention the docs were off.
History
Date User Action Args
2012-03-14 16:58:18Shane.Hansensetrecipients: + Shane.Hansen, georg.brandl, pitrou, docs@python
2012-03-14 16:58:18Shane.Hansensetmessageid: <1331744298.15.0.025379356395.issue14303@psf.upfronthosting.co.za>
2012-03-14 16:58:17Shane.Hansenlinkissue14303 messages
2012-03-14 16:58:17Shane.Hansencreate