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 xmorel
Recipients OverLordGoldDragon, asvetlov, xmorel, yselivanov
Date 2020-12-15.14:24:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The problem seems to be in the user code? As you were told by "Carreau", loggin.disable takes a logging level (an integer), since you're giving it a string which it dutifully stores, it blows up at the next logging call which happens to be in asyncio.

This is not an asyncio bug, nor is it a crash anymore than passing a broken key function to `sorted` is a *Python* crash.

At most it's an enancement request: `logging.disable` could raise a TypeError immediately or convert the value to a loglevel the way `setLevel` does instead of storing the broken value as-is (all it does currently is store the value it receives on the root logger without any check).
Date User Action Args
2020-12-15 14:24:28xmorelsetrecipients: + xmorel, asvetlov, yselivanov, OverLordGoldDragon
2020-12-15 14:24:28xmorelsetmessageid: <>
2020-12-15 14:24:28xmorellinkissue42644 messages
2020-12-15 14:24:28xmorelcreate