Benjamin Peterson <[EMAIL PROTECTED]> added the comment: 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.
---------- nosy: +benjamin.peterson, brett.cannon priority: -> high _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4180> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
