summaryrefslogtreecommitdiffstats
path: root/Lib/logging/__init__.py
Commit message (Collapse)AuthorAgeFilesLines
* bpo-36015: Handle StreamHandler representaton of stream with an integer name ↵Miss Islington (bot)2019-05-151-0/+2
| | | | | | | (GH-11908) (GH-13183) (cherry picked from commit ca87eebb22d202c33f3317cbf85059cadc64fa9f) Co-authored-by: Riccardo Magliocchetti <riccardo.magliocchetti@gmail.com>
* [3.7] bpo-36533: Reinit logging.Handler locks on fork(). (GH-12704) (GH-13170)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. (cherry picked from commit 64aa6d2000665efb1a2eccae176df9520bf5f5e6) Co-authored-by: Gregory P. Smith <greg@krypto.org> [Google LLC]
* bpo-36272: Logging now propagates RecursionError (GH-12312) (GH-12391)Miss Islington (bot)2019-03-181-0/+4
| | | | | (cherry picked from commit 65f64b1903ae85b97a30f514bbc1b7ce940c3af2) Co-authored-by: Rémi Lapeyre <remi.lapeyre@henki.fr>
* bpo-35046: do only one system call per line (logging.StreamHandler) ↵Miss Islington (bot)2018-10-231-2/+2
| | | | | (GH-10042) (GH-10050) (cherry picked from commit b7d62050e7d5fc208ae7673613da4f1f2bc565c4)
* bpo-6721: Hold logging locks across fork() (GH-4071) (#9291)Miss Islington (bot)2018-10-071-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. (cherry picked from commit 19003841e965bbf56fd06824d6093620c1b66f9e) Co-authored-by: Gregory P. Smith <greg@krypto.org> [Google]
* bpo-34415: Updated logging.Formatter docstring. (GH-8811) (GH-8817)Miss Islington (bot)2018-08-191-1/+2
| | | | (cherry picked from commit d3d3171da895d8cb880f23fae6be778f0ac23be7)
* bpo-33400: Clarified documentation to indicate no strict adherence to ISO ↵Miss Islington (bot)2018-05-281-8/+9
| | | | | | | 8601. (GH-6702) (GH-6704) (cherry picked from commit c4994dc00d9828a99510f3851da93b0e1c18361d) Co-authored-by: Vinay Sajip <vinay_sajip@yahoo.co.uk>
* 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.
* Closes #20242: Merged fix from 3.3.Vinay Sajip2014-01-131-7/+10
|\
| * Issue #20242: Fixed basicConfig() format strings for the alternative ↵Vinay Sajip2014-01-131-7/+10
| | | | | | | | formatting styles.
* | Closes #19523: Merged fix from 3.3.Vinay Sajip2013-11-151-1/+3
|\ \ | |/
| * Issue #19523: Closed FileHandler leak which occurred when delay was set.Vinay Sajip2013-11-151-1/+3
| |
* | Closes #18941: Merged fix from 3.3.Vinay Sajip2013-09-061-2/+3
|\ \ | |/
| * Issue #18941: Respected delay when doing rollover.Vinay Sajip2013-09-061-2/+3
| |
generated by cgit v0.12 at 2026-01-06 13:11:19 (GMT)