Message156759
I was looking at a somewhat unrelated issue and I bumped up against a similar situation with the warnings system.
I didn't look too much into it, but it appeared that warnings didn't get added to __warningregistry__ correctly. Though, when I set the stack level explicitly (to an incorrect value for the issue at hand), the warnings were caught by catch_warnings.
I don't know if it is related or not, but my assumption at the time was that smarter people than I had vetted warnings. =) |
|
Date |
User |
Action |
Args |
2012-03-25 16:39:22 | mcjeff | set | recipients:
+ mcjeff, jhylton, orsenthil, pitrou, nadeem.vawda, ezio.melotti, eric.araujo, neologix, python-dev |
2012-03-25 16:39:22 | mcjeff | set | messageid: <1332693562.32.0.931639129472.issue10050@psf.upfronthosting.co.za> |
2012-03-25 16:39:21 | mcjeff | link | issue10050 messages |
2012-03-25 16:39:21 | mcjeff | create | |
|