Message 212666 - Python tracker

Message212666

Author	yselivanov
Recipients	gvanrossum, vstinner, yselivanov
Date	2014-03-03.20:31:41
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1393878701.91.0.770562374062.issue20847@psf.upfronthosting.co.za>
In-reply-to

Content
Can we instead re-engineer asyncio logging to have logger calls in a separate thread? I.e. `logger` is a proxy object, that puts logging calls in a queue, and there would be another thread to block on the queue and do the actual logging. This way it won't really matter how logging is configured.

Content

Can we instead re-engineer asyncio logging to have logger calls in a separate thread?

I.e. `logger` is a proxy object, that puts logging calls in a queue, and there would be another thread to block on the queue and do the actual logging. This way it won't really matter how logging is configured.

History
Date	User	Action	Args
2014-03-03 20:31:41	yselivanov	set	recipients: + yselivanov, gvanrossum, vstinner
2014-03-03 20:31:41	yselivanov	set	messageid: <1393878701.91.0.770562374062.issue20847@psf.upfronthosting.co.za>
2014-03-03 20:31:41	yselivanov	link	issue20847 messages
2014-03-03 20:31:41	yselivanov	create