➜

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 r.david.murray
Recipients brett.cannon, eric.araujo, eric.smith, r.david.murray, xmorel
Date 2010-02-23.03:48:51
SpamBayes Score 2.0072277e-12
Marked as misclassified No
Message-id <1266896933.51.0.066366717112.issue7976@psf.upfronthosting.co.za>
In-reply-to
Content 
I believe the ability to log warning messages was added recently, but that it does not give you an control over what warnings are *generated*, just what happens to them (that is, allowing you to log them).

On the other hand, what is the motivation for wanting this control?  In 2.7/3.2, warnings will be silent by default.  Is it that you want the command/framework author to be able to allow users to turn warnings on?  This seems like an infrequent enough use case that it is probably better as a recipe rather than in the core (perhaps an example in the docs for warnings, but I'm not sure about that even).

In addition,
History
Date User Action Args
2010-02-23 03:48:53r.david.murraysetrecipients: + r.david.murray, brett.cannon, eric.smith, eric.araujo, xmorel
2010-02-23 03:48:53r.david.murraysetmessageid: <1266896933.51.0.066366717112.issue7976@psf.upfronthosting.co.za>
2010-02-23 03:48:51r.david.murraylinkissue7976 messages
2010-02-23 03:48:51r.david.murraycreate