[issue41857] Document timeout arguments to poll() in select module

Change by Zane Bitter : -- keywords: +patch pull_requests: +21446 stage: -> patch review pull_request: https://github.com/python/cpython/pull/22406 ___ Python tracker <https://bugs.python.org/issu

[issue41857] Document timeout arguments to poll() in select module

New submission from Zane Bitter : The select.poll.poll() and select.devpoll.poll() methods don't have their timeout arguments documented in their docstrings. In both cases the argument is in milliseconds, whereas the timeout arguments to select.kqueue.control() and select.epoll.poll() a

[issue37857] Setting logger.level directly has no effect due to caching in 3.7+

Zane Bitter added the comment: In turns out that setting the level directly is used in the standard library, so we definitely have a bug here that needs fixing in 3.7 & 3.8. Obviously the fix could be just to stop doing that in the standard library, but I'd argue that this is even

[issue37857] Setting logger.level directly has no effect due to caching in 3.7+

Zane Bitter added the comment: > It feels wrong to do this as a band-aid to help out people who didn't do the > right thing. I mean... are we here to punish people for making mistakes by sending them to schroedinbug purgatory, or are we here to help them upgrade to the lat

[issue37857] Setting logger.level directly has no effect due to caching in 3.7+

Zane Bitter added the comment: > That code in the wild that sets the level attribute directly is wrong and > should be changed, right? It definitely should be changed (and in our case we did change it once we found it). Whether it's "wrong" is more of a philosophical

[issue37857] Setting logger.level directly has no effect due to caching in 3.7+

Change by Zane Bitter : -- keywords: +patch pull_requests: +15008 stage: -> patch review pull_request: https://github.com/python/cpython/pull/15286 ___ Python tracker <https://bugs.python.org/issu

[issue30962] Add caching to logging.Logger.isEnabledFor()

Change by Zane Bitter : -- pull_requests: +15009 pull_request: https://github.com/python/cpython/pull/15286 ___ Python tracker <https://bugs.python.org/issue30

[issue37857] Setting logger.level directly has no effect due to caching in 3.7+

New submission from Zane Bitter : This is a related issue to bug 34269, in the sense that it is also due to the caching added by the fix for bug 30962. In this case, the bug is triggered by setting the public 'level' attribute of a logging.Logger object, instead of calling th

[issue28603] traceback module can't format/print unhashable exceptions

Zane Bitter added the comment: I also encountered this issue, and I'd like to further note that it is extraordinarily difficult to debug without access to stderr. If your logging facility uses the traceback module then it will be unable to record both the original (unhashable) exception

[issue28603] traceback module can't format/print unhashable exceptions

Change by Zane Bitter : -- pull_requests: +3988 ___ Python tracker <https://bugs.python.org/issue28603> ___ ___ Python-bugs-list mailing list Unsubscribe: