> What should resetwarnings really do? Offhand it looks most
> reasonable to me to move the module initialization code
>
> _processoptions(sys.warnoptions)
> filterwarnings("ignore", category=OverflowWarning, append=1)
>
> into the body of resetwarnings(), then call the latter from the
> initialization block.
>
> Objections?
If you do that, side effects from _processoptions(), like warnings
about incomprehensible -W options, are issued each time.
I'd prefer it if you didn't try to call resetwarnings() at all.
That's for the main() app only.
--Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4