-
-
Notifications
You must be signed in to change notification settings - Fork 29.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
warnings in interactive sessions #43816
Comments
Carried over from Patch bpo-1538956 description: During testing I found that the warning registry I suppose this is enough for debugging code, but it The reason is that the warning framework registers In general, it might be a better idea to have a single |
Not a bad idea, although it would require some work to make it work in a |
Is there still any interest in this? |
Looks reasonable to me. Perhaps we should port the solution from IPython: |
As a user, what would I actually gain from being warned more than once per session that a particular API I'm using is deprecated? If I want that behaviour, I can already opt in to it by doing "warnings.simplefilter('always')". As things stand, the perpetually reset line counter just means that the effective default at the REPL is "warnings.simplefilter('module:::main')" |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: