Understood!  FYI, we worked around this caching issue explicitly in our code.  This wound up being simpler than supporting a hacked version of the logger.

Thanks for looking into this!

On Mon, Apr 11, 2011 at 1:54 AM, Vinay Sajip <report@bugs.python.org> wrote:

Vinay Sajip <vinay_sajip@yahoo.co.uk> added the comment:

I'll regretfully have to mark this as wontfix, since adding threading interlocks for correct operation in multi-threaded environments will negate the performance benefit.

----------
resolution:  -> wont fix
status: open -> closed

_______________________________________
Python tracker <report@bugs.python.org>
<http://bugs.python.org/issue11369>
_______________________________________