[issue12174] Multiprocessing logging levels unclear

Change by Irit Katriel : -- resolution: -> out of date stage: patch review -> resolved status: open -> closed ___ Python tracker ___ __

[issue12174] Multiprocessing logging levels unclear

Vinay Sajip added the comment: I'd like to close this issue as out of date - anyone object? -- ___ Python tracker ___ ___ Python-bu

[issue12174] Multiprocessing logging levels unclear

Changes by Davin Potts : -- nosy: +davin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.or

[issue12174] Multiprocessing logging levels unclear

Camilla Montonen added the comment: This issue raises the fact that the 2.X documentation lists two logging levels (SUBDEBUG and SUBWARNING) without explaining how these two fit into the logging hierarchy of the logging levels provided by the standard library logging module (ie, is SUBDEBUG be

[issue12174] Multiprocessing logging levels unclear

Vinay Sajip added the comment: > Should there be another issue opened to do something about the extra logging > levels? IMO they shouldn't have been added in the first place, but I'm not sure if they're part of the public API and hence subject to backward-compatibility constraints. It would

[issue12174] Multiprocessing logging levels unclear

Petri Lehtinen added the comment: Should there be another issue opened to do something about the extra logging levels? -- ___ Python tracker ___ ___

[issue12174] Multiprocessing logging levels unclear

Vinay Sajip added the comment: Although the reference docs don't list the numeric values of logging levels, this happened during reorganising of the docs. The table has moved to the HOWTO: http://docs.python.org/howto/logging.html#logging-levels That said, I don't understand the need for spec

[issue12174] Multiprocessing logging levels unclear

Changes by Petri Lehtinen : -- keywords: +needs review stage: -> patch review versions: +Python 3.2 ___ Python tracker ___ ___ Python

[issue12174] Multiprocessing logging levels unclear

Petri Lehtinen added the comment: R. David Murray wrote: > I think it would be good to mention the numeric levels in the text as well > (in parenthesis, perhaps), unless the rest of the logging docs no longer > refer to the numeric levels. AFAICS, there are no numbers in the logging docs anym

[issue12174] Multiprocessing logging levels unclear

R. David Murray added the comment: I think it would be good to mention the numeric levels in the text as well (in parenthesis, perhaps), unless the rest of the logging docs no longer refer to the numeric levels. -- nosy: +r.david.murray ___ Python

[issue12174] Multiprocessing logging levels unclear

Changes by Nick Coghlan : -- nosy: +jnoller, ncoghlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue12174] Multiprocessing logging levels unclear

Petri Lehtinen added the comment: Converted the patch by JJeffries to a valid format. -- Added file: http://bugs.python.org/file22110/multiprocessing_logging_2.patch ___ Python tracker

[issue12174] Multiprocessing logging levels unclear

Petri Lehtinen added the comment: The patch is in an invalid format. See http://docs.python.org/devguide/patch.html for instructions on working with patches. If you cannot/won't use Mercurial, use two separate directories for original and modified cpython source tree, and invoke: diff -u

[issue12174] Multiprocessing logging levels unclear

Changes by JJeffries : -- keywords: +patch Added file: http://bugs.python.org/file22106/multiprocessing_logging.patch ___ Python tracker ___ _

[issue12174] Multiprocessing logging levels unclear

Petri Lehtinen added the comment: It seems that the documentation of logging no longer gives a table with numeric values for levels (I remember seeing it before). Maybe it would be most useful to remove the table from multiprocessing documentation and state it explicitly that "SUBDEBUG is low

[issue12174] Multiprocessing logging levels unclear

New submission from JJeffries : It is unclear without reference to the logging module where the multiprocessing logging levels fit in the normal logging provided by the logging module, even though it says above the table "The table below illustrates where theses fit in the normal level hierarc