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 neologix
Recipients neologix, ryan003, victorpoluceno, vstinner
Date 2011-05-21.11:11:42
SpamBayes Score 4.31165e-08
Marked as misclassified No
Message-id <1305976304.06.0.0730772252186.issue5715@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks for reporting this, the current behaviour is clearly wrong. The child process doesn't need to - and shouldn't - inherit the server socket.
The custom idiom when writting such code is to close the new socket (well, in TCP) in the parent process, and close the server socket in the child process.
That's what the attached patch does.
Since I really doubt anyone using socketserver ever used the server's socket from the handler, this shouldn't be a problem for existing code (and the server's socket was never documented to be usable from the request handler).
History
Date User Action Args
2011-05-21 11:11:44neologixsetrecipients: + neologix, vstinner, ryan003, victorpoluceno
2011-05-21 11:11:44neologixsetmessageid: <1305976304.06.0.0730772252186.issue5715@psf.upfronthosting.co.za>
2011-05-21 11:11:43neologixlinkissue5715 messages
2011-05-21 11:11:43neologixcreate