Author vinay.sajip
Recipients JJeffries, docs@python, jnoller, ncoghlan, petri.lehtinen, r.david.murray, vinay.sajip
Date 2011-08-27.14:27:33
SpamBayes Score 3.4172e-05
Marked as misclassified No
Message-id <1314455255.67.0.948973815229.issue12174@psf.upfronthosting.co.za>
In-reply-to
Content
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 special logging levels in the multiprocessing package. From the section following the one linked to above:

"Defining your own levels is possible, but should not be necessary, as the existing levels have been chosen on the basis of practical experience. However, if you are convinced that you need custom levels, great care should be exercised when doing this, and it is possibly *a very bad idea to define custom levels if you are developing a library*. That’s because if multiple library authors all define their own custom levels, there is a chance that the logging output from such multiple libraries used together will be difficult for the using developer to control and/or interpret, because a given numeric value might mean different things for different libraries."
History
Date User Action Args
2011-08-27 14:27:35vinay.sajipsetrecipients: + vinay.sajip, ncoghlan, jnoller, r.david.murray, docs@python, JJeffries, petri.lehtinen
2011-08-27 14:27:35vinay.sajipsetmessageid: <1314455255.67.0.948973815229.issue12174@psf.upfronthosting.co.za>
2011-08-27 14:27:34vinay.sajiplinkissue12174 messages
2011-08-27 14:27:33vinay.sajipcreate