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 benjamin.peterson
Recipients benjamin.peterson, brett.cannon, exarkun
Date 2008-10-22.22:19:01
SpamBayes Score 4.315034e-09
Marked as misclassified No
Message-id <>
If you didn't raise the warning before using the simple filter, this
would have worked. The undesired behavior is because of
__warningsregistry__. It is set the first time the warning is emitted.
When the second warning comes through, the filter isn't even looked at.
I think the best way to fix this is to invalidate __warningsregistry__
when a filter is used. It would probably be best to store warnings data
in a global then instead of on the module, so it is easy to invalidate.
Date User Action Args
2008-10-22 22:19:04benjamin.petersonsetrecipients: + benjamin.peterson, brett.cannon, exarkun
2008-10-22 22:19:04benjamin.petersonsetmessageid: <>
2008-10-22 22:19:03benjamin.petersonlinkissue4180 messages
2008-10-22 22:19:02benjamin.petersoncreate