Message156759
| Author |
mcjeff |
| Recipients |
eric.araujo, ezio.melotti, jhylton, mcjeff, nadeem.vawda, neologix, orsenthil, pitrou, python-dev |
| Date |
2012年03月25日.16:39:21 |
| SpamBayes Score |
6.0909015e-06 |
| Marked as misclassified |
No |
| Message-id |
<1332693562.32.0.931639129472.issue10050@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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. =) |
|