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 brett.cannon
Recipients benjamin.peterson, brett.cannon, exarkun
Date 2008-10-22.22:52:13
SpamBayes Score 0.00010931149
Marked as misclassified No
Message-id <bbaeab100810221552i81feedi4e9178aeb3065294@mail.gmail.com>
In-reply-to <1224715148.08.0.571756692826.issue4180@psf.upfronthosting.co.za>
Content
On Wed, Oct 22, 2008 at 3:39 PM, Benjamin Peterson
<report@bugs.python.org> wrote:
>
> Benjamin Peterson <musiccomposition@gmail.com> added the comment:
>
> Oh, do we not consider __warningsregistry__ an implementation detail?
>

I guess you could view it that way. I just know I find it extremely
annoying for testing for the exact reasons JP mentions; it's
unexpected if you don't know about it.

If we made __warningsregistry__  about just recording what warnings
have been raised and not include filter information (which I what I
think you are suggesting) then it would still server its purpose,
albeit for probably a small performance penalty. Probably whomever
came up with it over-optimized and just didn't realize that it might
play havoc with testing.
History
Date User Action Args
2008-10-22 22:52:15brett.cannonsetrecipients: + brett.cannon, exarkun, benjamin.peterson
2008-10-22 22:52:14brett.cannonlinkissue4180 messages
2008-10-22 22:52:13brett.cannoncreate