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 eantelman
Recipients Frans, eantelman, lowell87, mramahi77, neyro, rcronk, vinay.sajip
Date 2009-07-01.19:15:32
SpamBayes Score 5.32595e-09
Marked as misclassified No
Message-id <1246475737.03.0.0208427221237.issue4749@psf.upfronthosting.co.za>
In-reply-to
Content
The really annoying this about handle inheritance is that even if a 
subprocess is never referencing or using logging there can be an open 
file handle conflict due to the default inheratence.

Another tack from modifying Popen, 

I looked at the forking.py of multiprocessing and observed the 
techniques for changing the inheratance attribute of files handles 
using the _subprocess wrapper to the NT DuplicateHandle call.

Then by replacing the _open of the FileHandler to ensure handles are 
open non-inheritable I can ensure that log files are not inherited. 
This preserves the behavior of everything else. 

I attached the NT/Multiprocessing safe version of a RotatingFileHandler 
class
History
Date User Action Args
2009-07-01 19:15:37eantelmansetrecipients: + eantelman, vinay.sajip, mramahi77, lowell87, neyro, rcronk, Frans
2009-07-01 19:15:37eantelmansetmessageid: <1246475737.03.0.0208427221237.issue4749@psf.upfronthosting.co.za>
2009-07-01 19:15:33eantelmanlinkissue4749 messages
2009-07-01 19:15:33eantelmancreate