Message 170698 - 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	ncoghlan
Recipients	ncoghlan, vinay.sajip
Date	2012-09-19.03:45:14
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1348026315.23.0.981268013448.issue15960@psf.upfronthosting.co.za>
In-reply-to

Content
The particular app that is getting affected is clearing out and rebuilding the logging configuration without restarting in response to a notification that the application config has changed. This was working OK on 2.6, but started misbehaving when ported to 2.7. It's http://pypi.python.org/pypi/ConcurrentLogHandler that's calling self.stream.flush() inside release(), and I suspect that is a bug on that side as well. It's also possible that we should just be skipping the use of ConcurrentLogHandler entirely on 2.7, but I haven't looked into the feasibility of that as yet. This specific bug report is just because I noticed that the stdlib is trying to be tolerant of handler misbehaviour, but not quite succeeding in this particular case. Perhaps we should be writing something out to stderr when ignoring one of these errors?

The particular app that is getting affected is clearing out and rebuilding the logging configuration without restarting in response to a notification that the application config has changed. This was working OK on 2.6, but started misbehaving when ported to 2.7.

It's http://pypi.python.org/pypi/ConcurrentLogHandler that's calling self.stream.flush() inside release(), and I suspect that *is* a bug on that side as well.

It's also possible that we should just be skipping the use of ConcurrentLogHandler entirely on 2.7, but I haven't looked into the feasibility of that as yet.

This specific bug report is just because I noticed that the stdlib is *trying* to be tolerant of handler misbehaviour, but not quite succeeding in this particular case. Perhaps we should be writing something out to stderr when ignoring one of these errors?

History
Date	User	Action	Args
2012-09-19 03:45:15	ncoghlan	set	recipients: + ncoghlan, vinay.sajip
2012-09-19 03:45:15	ncoghlan	set	messageid: <1348026315.23.0.981268013448.issue15960@psf.upfronthosting.co.za>
2012-09-19 03:45:14	ncoghlan	link	issue15960 messages
2012-09-19 03:45:14	ncoghlan	create