[issue37258] Logging cache not cleared properly when setting level

2019-06-19 Thread Vinay Sajip
Change by Vinay Sajip : -- stage: -> resolved ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue37258] Logging cache not cleared properly when setting level

2019-06-19 Thread Vinay Sajip
Change by Vinay Sajip : -- stage: resolved -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue37258] Logging cache not cleared properly when setting level

2019-06-19 Thread Vinay Sajip
Change by Vinay Sajip : -- stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailin

[issue37258] Logging cache not cleared properly when setting level

2019-06-19 Thread Vinay Sajip
Vinay Sajip added the comment: New changeset 95ff622028b4f5d2eefbff557eadbb08fbcd42b1 by Vinay Sajip (Miss Islington (bot)) in branch '3.8': bpo-37258: Not a bug, but added a unit test and updated documentation. (GH-14229) (GH-14230) https://github.com/python/cpython/commit/95ff622028b4f5d2e

[issue37258] Logging cache not cleared properly when setting level

2019-06-19 Thread Vinay Sajip
Vinay Sajip added the comment: New changeset 9eb4b2c8a3387ea901dad793e8d5586880a5968e by Vinay Sajip (Miss Islington (bot)) in branch '3.7': bpo-37258: Not a bug, but added a unit test and updated documentation. (GH-14229) (GH-14231) https://github.com/python/cpython/commit/9eb4b2c8a3387ea90

[issue37258] Logging cache not cleared properly when setting level

2019-06-19 Thread miss-islington
Change by miss-islington : -- pull_requests: +14066 pull_request: https://github.com/python/cpython/pull/14230 ___ Python tracker ___ __

[issue37258] Logging cache not cleared properly when setting level

2019-06-19 Thread miss-islington
Change by miss-islington : -- pull_requests: +14067 pull_request: https://github.com/python/cpython/pull/14231 ___ Python tracker ___ __

[issue37258] Logging cache not cleared properly when setting level

2019-06-19 Thread Vinay Sajip
Vinay Sajip added the comment: New changeset 015000165373f8db263ef5bc682f02d74e5782ac by Vinay Sajip in branch 'master': bpo-37258: Not a bug, but added a unit test and updated documentation. (GH-14229) https://github.com/python/cpython/commit/015000165373f8db263ef5bc682f02d74e5782ac -

[issue37258] Logging cache not cleared properly when setting level

2019-06-19 Thread Vinay Sajip
Change by Vinay Sajip : -- keywords: +patch pull_requests: +14065 stage: -> patch review pull_request: https://github.com/python/cpython/pull/14229 ___ Python tracker ___

[issue37258] Logging cache not cleared properly when setting level

2019-06-19 Thread Vinay Sajip
Vinay Sajip added the comment: This is not actually a bug, but happens because the logger is instantiated directly, rather than through logging.getLogger(...). Because of the direct instantiation, the logger cache isn't tracked via setLevel() - because the logger doesn't end up in logging.ma

[issue37258] Logging cache not cleared properly when setting level

2019-06-13 Thread Raymond Hettinger
Change by Raymond Hettinger : -- assignee: -> vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue37258] Logging cache not cleared properly when setting level

2019-06-13 Thread Karthikeyan Singaravelan
Karthikeyan Singaravelan added the comment: A unittest patch for this issue. This occurs in master and 3.8 too. diff --git a/Lib/test/test_logging.py b/Lib/test/test_logging.py index 50148dc2f2..30fd9ee37a 100644 --- a/Lib/test/test_logging.py +++ b/Lib/test/test_logging.py @@ -4172,6 +4172,27

[issue37258] Logging cache not cleared properly when setting level

2019-06-12 Thread Karthikeyan Singaravelan
Change by Karthikeyan Singaravelan : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue37258] Logging cache not cleared properly when setting level

2019-06-12 Thread David Wang
New submission from David Wang : If you call setLevel() on a subclass of logging.Logger, it does not reset the cache for that logger. This mean that if you make some logging calls, then call setLevel(), the logger still acts like it still has its old level. See the attached python file for a