➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vinay.sajip
Recipients JJeffries, docs@python, jnoller, ncoghlan, petri.lehtinen, r.david.murray, vinay.sajip
Date 2011-10-18.20:05:22
SpamBayes Score 8.83498e-08
Marked as misclassified No
Message-id <1318968319.2616.YahooMailNeo@web25806.mail.ukl.yahoo.com>
In-reply-to <1318926357.56.0.330697503707.issue12174@psf.upfronthosting.co.za>
Content 
> 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 be nice to hear a justification for them from Jesse (or someone else). Of course levels are a bit subjective and logging supports user-defined levels for special cases, but using multiple libs with different added levels would be a headache. I think at least the stdlib should stick to the standard levels.
History
Date User Action Args
2011-10-18 20:05:23vinay.sajipsetrecipients: + vinay.sajip, ncoghlan, jnoller, r.david.murray, docs@python, JJeffries, petri.lehtinen
2011-10-18 20:05:22vinay.sajiplinkissue12174 messages
2011-10-18 20:05:22vinay.sajipcreate