Message 189400 - 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	vinay.sajip
Recipients	Julien.Palard, joshpurvis, sbt, vinay.sajip
Date	2013-05-16.18:35:49
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1368729349.95.0.66851530572.issue17981@psf.upfronthosting.co.za>
In-reply-to

Content
> The old socket's destructor closes the fd of the new socket. Aha! Nice one. But what's the correct fix? I suppose a self.sock = None before every self.sock = socket.socket call would fix seem this, and while I can certainly make this change in SysLogHandler, isn't this a more general problem?

> The old socket's destructor closes the fd of the new socket.

Aha! Nice one. But what's the correct fix? I suppose a

self.sock = None

before every self.sock = socket.socket call would fix seem this, and while I can certainly make this change in SysLogHandler, isn't this a more general problem?

History
Date	User	Action	Args
2013-05-16 18:35:49	vinay.sajip	set	recipients: + vinay.sajip, sbt, Julien.Palard, joshpurvis
2013-05-16 18:35:49	vinay.sajip	set	messageid: <1368729349.95.0.66851530572.issue17981@psf.upfronthosting.co.za>
2013-05-16 18:35:49	vinay.sajip	link	issue17981 messages
2013-05-16 18:35:49	vinay.sajip	create