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 Decorater
Recipients Decorater, Rosuav, abarry, ethan.furman, georg.brandl, ncoghlan, python-dev, serhiy.storchaka, xiang.zhang
Date 2016-08-15.03:25:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1471231555.1.0.229039007336.issue26823@psf.upfronthosting.co.za>
In-reply-to
Content
3.6 would make thread exceptions not print out to console or at least be configured to make them logged with the logging module in threading.py for 3.6? because I would like it to use the logger. Oh and how can I get the logs from the logging module from 2 different libs in 1 module?

Like I can get the logs from 1 module just fine.
However if I try to get from things (lets say from asyncio (then it would return nothing).
History
Date User Action Args
2016-08-15 03:25:55Decoratersetrecipients: + Decorater, georg.brandl, ncoghlan, ethan.furman, python-dev, Rosuav, serhiy.storchaka, xiang.zhang, abarry
2016-08-15 03:25:55Decoratersetmessageid: <1471231555.1.0.229039007336.issue26823@psf.upfronthosting.co.za>
2016-08-15 03:25:55Decoraterlinkissue26823 messages
2016-08-15 03:25:54Decoratercreate