summaryrefslogtreecommitdiffstats
path: root/Lib/logging/__init__.py
Commit message (Collapse)AuthorAgeFilesLines
* bpo-39198: Ensure logging global lock is released on exception in ↵Miss Islington (bot)2020-01-071-6/+9
| | | | | isEnabledFor (GH-17689) (GH-17897) (cherry picked from commit 950c6795aa0ffa85e103a13e7a04e08cb34c66ad)
* bpo-36015: Handle StreamHandler representaton of stream with an integer name ↵Riccardo Magliocchetti2019-05-071-0/+2
| | | | (GH-11908)
* bpo-36533: Reinit logging.Handler locks on fork(). (GH-12704)Gregory P. Smith2019-05-071-36/+25
| | | | | Instead of attempting to acquire and release them all across fork which was leading to deadlocks in some applications that had chained their own handlers while holding multiple locks.
* bpo-36793: Remove unneeded __str__ definitions. (GH-13081)Serhiy Storchaka2019-05-061-3/+1
| | | | Classes that define __str__ the same as __repr__ can just inherit it from object.
* bpo-36272: Logging now propagates RecursionError (GH-12312)Rémi Lapeyre2019-03-151-0/+4
|
* bpo-35046: do only one system call per line (logging.StreamHandler) (GH-10042)Josh Snyder2018-10-231-2/+2
|
* bpo-34844: logging.Formatter enhancement - Ensure style and format string ↵BNMetrics2018-10-151-5/+63
| | | | matches in logging.Formatter (GH-9703)
* bpo-6721: Hold logging locks across fork() (GH-4071)Gregory P. Smith2018-09-141-0/+50
| | | | | | | | | bpo-6721: When os.fork() was called while another thread holds a logging lock, the child process may deadlock when it tries to log. This fixes that by acquiring all logging locks before fork and releasing them afterwards. A regression test that fails before this change is included. Within the new unittest itself: There is a small _potential_ due to mixing of fork and a thread in the child process if the parent's thread happened to hold a non-reentrant library call lock (malloc?) when the os.fork() happens. buildbots and time will tell if this actually manifests itself in this test or not. :/ A functionality test that avoids that would be a challenge. An alternate test that isn't trying to produce the deadlock itself but just checking that the release and acquire calls are made would be the next best alternative if so.
* bpo-34415: Updated logging.Formatter docstring. (GH-8811)Vinay Sajip2018-08-191-1/+2
|
* bpo-33897: Add a 'force' keyword argument to logging.basicConfig(). (GH-7873)Dong-hee Na2018-06-251-2/+14
|
* bpo-33165: Added stacklevel parameter to logging APIs. (GH-7424)Vinay Sajip2018-06-051-3/+10
|
* bpo-33606: improve logging performance when logger is disabled (GH-7285)Timo Furrer2018-06-011-0/+3
| | | A check has been added in Logger.isEnabledFor() to return False when the logger is disabled. This avoids unnecessary work being done when a disabled logger is used.
* bpo-33400: Clarified documentation to indicate no strict adherence to ISO ↵Vinay Sajip2018-05-041-8/+9
| | | | 8601. (GH-6702)
* bpo-31457: Don't omit inner ``process()`` calls with nested LogAdapters (#4044)Łukasz Langa2017-10-191-1/+5
| | | | | | | | | | | This used to be the case on Python 2. Commit 212b590e118e3650b596917021ed9612a918180b changed the implementation for Python 3, making the `log()` method of LogAdapter call `logger._log()` directly. This makes nested log adapters not execute their ``process()`` method. This patch fixes the issue. Also, now proxying `name`, too, to make `repr()` work with nested log adapters. New tests added.
* bpo-31457: Make the `LoggerAdapter.manager` property settable (#4042)Łukasz Langa2017-10-191-1/+1
| | | | Due to a bug in the initial fix, the setter was in fact creating a different property. This is now fixed.
* bpo-31457: Allow for nested LoggerAdapter objects (#3551)Łukasz Langa2017-09-141-0/+21
| | | | | | Some of the proxied methods use internal Logger state which isn't proxied, causing failures if an adapter is applied to another adapter. This commit fixes the issue, adds a new test for the use case.
* bpo-31370: Remove support for threads-less builds (#3385)Antoine Pitrou2017-09-071-14/+4
| | | | | | * Remove Setup.config * Always define WITH_THREAD for compatibility.
* Updated LoggerAdapter.isEnabledFor to take advantage of caching. (GH-2951)Vinay Sajip2017-07-301-3/+1
|
* bpo-30522: Implemented a method to allow setting a logging.StreamHander's ↵Vinay Sajip2017-07-301-0/+20
| | | | stream. (GH-2921)
* bpo-30962: Added caching to Logger.isEnabledFor() (GH-2752)Avram Lubkin2017-07-301-3/+27
|
* bpo-30520: Implemented pickling for loggers. (#1956)Vinay Sajip2017-06-061-2/+13
| | | Implemented pickling for loggers.
* bpo-30144: Import collections ABC from collections.abc rather than ↵Serhiy Storchaka2017-04-241-3/+3
| | | | collections. (#1263)
* Issue #29220: Merged fixes from 3.6.Vinay Sajip2017-01-111-5/+6
|\
| * Issue #292Merged fixes from 3.5.Vinay Sajip2017-01-111-3/+8
| |\
| | * Issue #29220: Improved fix and test.Vinay Sajip2017-01-111-3/+8
| | |
| | * Fixes #27937: optimise code used in all logging calls.Vinay Sajip2016-09-031-4/+5
| | |
* | | Closes #29220: Fixed regression in logging.getLevelName().Vinay Sajip2017-01-111-3/+7
| | |
* | | Closes #28524: added default level for logging.disable().Vinay Sajip2016-12-311-1/+1
|/ /
* | Closes #27935: returned numeric value for 'FATAL' logging level.Vinay Sajip2016-09-031-0/+1
| |
* | Fixes #27937: optimise code used in all logging calls.Vinay Sajip2016-09-031-2/+3
| |
* | Closes #27650: Implemented repr methods for logging objects.Vinay Sajip2016-08-061-0/+27
| |
* | Closes #27493: accepted Path objects in file handlers for logging.Vinay Sajip2016-07-221-2/+4
| |
* | merge with 3.5Georg Brandl2016-02-251-2/+2
|\ \ | |/
| * Closes #26435: fix syntax in directives. Thanks to Jakub Stasiak.Georg Brandl2016-02-251-2/+2
| |
* | Issue #23883: Add missing APIs to __all__; patch by Jacek KołodziejMartin Panter2015-11-141-2/+3
|/
* Issue #23865: close() methods in multiple modules now are idempotent and moreSerhiy Storchaka2015-04-101-8/+13
|\ | | | | | | | | robust at shutdown. If needs to release multiple resources, they are released even if errors are occured.
| * Issue #23865: close() methods in multiple modules now are idempotent and moreSerhiy Storchaka2015-04-101-8/+13
| | | | | | | | | | robust at shutdown. If needs to release multiple resources, they are released even if errors are occured.
* | Issue #23207: merged fix from 3.4.Vinay Sajip2015-03-181-1/+1
|\ \ | |/
| * Issue #23207: Improved kwarg validation.Vinay Sajip2015-03-181-1/+1
| |
* | Closes #23207: logging.basicConfig() now does additional validation of its ↵Vinay Sajip2015-01-231-8/+11
|\ \ | |/ | | | | arguments.
| * Issue #23207: logging.basicConfig() now does additional validation of its ↵Vinay Sajip2015-01-231-8/+11
| | | | | | | | arguments.
* | Closes #21980: Added a __repr__ for LogRecord.Vinay Sajip2015-01-061-2/+4
| |
* | Closes #23151: Removed unnecessary initialization.Vinay Sajip2015-01-061-2/+0
| |
* | Closes #20537: logging methods now accept an exception instance as well as a ↵Vinay Sajip2014-09-141-10/+9
|/ | | | Boolean value or exception tuple. Thanks to Yury Selivanov for the patch.
* Issue #22386: fixed regression.Vinay Sajip2014-09-111-1/+2
|
* Issue #21709: Improved implementation to cover the frozen module case.Vinay Sajip2014-06-121-28/+34
|
* Issue #21709: Remove references to __file__ when part of a frozen application.Vinay Sajip2014-06-111-2/+2
|
* Issue #21172: isinstance check relaxed from dict to collections.Mapping.Vinay Sajip2014-04-101-2/+9
|
* Issue #21149: Improved thread-safety in logging cleanup during interpreter ↵Vinay Sajip2014-04-041-8/+9
| | | | shutdown.
* Closes #20918: Added handling for exceptions during fallback output of ↵Vinay Sajip2014-03-141-4/+12
| | | | logging exceptions.
generated by cgit v0.12 at 2026-01-06 10:48:14 (GMT)