[issue1765140] logging: delay_fh option and configuration kwargs

Vinay Sajip added the comment: Added optional delay argument to FileHandler and subclasses. -- resolution: -> fixed status: open -> closed _ Tracker <[EMAIL PROTECTED]> _ _

[issue1765140] logging: delay_fh option and configuration kwargs

Chris Leary added the comment: Ah, I see what the miscommunication is now. Yes, implementing the feature as you suggested would give the user the ability to specify the delayed handle-opening /within/ the configuration file. What I had intended was a way to load/inspect a file configuration with

[issue1765140] logging: delay_fh option and configuration kwargs

Vinay Sajip added the comment: I'm not sure I agree with "If fileConfig has no delay_fh option, fileConfig() would create the FileHandlers with delay_fh as False". fileConfig will create the FileHandlers using the args= section entry to pass to the constructor. Hence, by specifying True for this

[issue1765140] logging: delay_fh option and configuration kwargs

Chris Leary added the comment: Hi Vinay, I was actually trying to address a use case where the delay_fh option in the fileConfig() would be necessary. Let's say I'm running a simulator that I run many instances of at once. The logging configuration is extensive, so I want to use a configuration

[issue1765140] logging: delay_fh option and configuration kwargs

Vinay Sajip added the comment: Thanks for the patch. I think it would be simpler to just implement an optional delay parameter in FileHandler and its subclasses: then the configuration stuff need not be touched at all, since the delay parameter can be specified in the configuration file. There wo