Message75117
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:04 | benjamin.peterson | set | recipients:
+ benjamin.peterson, brett.cannon, exarkun |
2008-10-22 22:19:04 | benjamin.peterson | set | messageid: <1224713944.24.0.958949000156.issue4180@psf.upfronthosting.co.za> |
2008-10-22 22:19:03 | benjamin.peterson | link | issue4180 messages |
2008-10-22 22:19:02 | benjamin.peterson | create | |
|