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 sbt
Recipients Julien.Palard, joshpurvis, sbt, vinay.sajip
Date 2013-05-16.19:17:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1368731851.26.0.104781188296.issue17981@psf.upfronthosting.co.za>
In-reply-to
Content
Rather than

    self.sock = None

I would do

    self.sock.close()

which should work better for non-refcounted Pythons.

Of course it would be better to do this immediately after forking (i.e. before any more fds are created), otherwise you could still accidentally zap the fd of some other object.

If you can't do this immediately after forking then maybe it is better to move inherited potentially broken objects to a garbage list to prevent garbage collection.
History
Date User Action Args
2013-05-16 19:17:31sbtsetrecipients: + sbt, vinay.sajip, Julien.Palard, joshpurvis
2013-05-16 19:17:31sbtsetmessageid: <1368731851.26.0.104781188296.issue17981@psf.upfronthosting.co.za>
2013-05-16 19:17:31sbtlinkissue17981 messages
2013-05-16 19:17:31sbtcreate