Skip to content
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

Default warnings behaviour #390

Open
alexmojaki opened this issue Sep 26, 2022 · 0 comments
Open

Default warnings behaviour #390

alexmojaki opened this issue Sep 26, 2022 · 0 comments

Comments

@alexmojaki
Copy link
Owner

friendly-traceback filters all warnings - see friendly-traceback/friendly-traceback#175. In some ways this is a good thing, e.g:

>>> import warnings
>>> warnings.simplefilter("default")
>>> import pandas
<frozen importlib._bootstrap>:914: ImportWarning: _SixMetaPathImporter.find_spec() not found; falling back to find_module()
<frozen importlib._bootstrap>:914: ImportWarning: _SixMetaPathImporter.find_spec() not found; falling back to find_module()
<frozen importlib._bootstrap>:914: ImportWarning: _SixMetaPathImporter.find_spec() not found; falling back to find_module()
>>> []()
/my_program_5.py:1: SyntaxWarning: 'list' object is not callable; perhaps you missed a comma?
  []()
/my_program_5.py:1: SyntaxWarning: 'list' object is not callable; perhaps you missed a comma?
  []()
>>> 

Ideally the behaviour should match the standard so that the warnings module works as expected and users can see potentially useful warnings, but at the same time this needs to be done in a way that avoids spurious noise and duplicates like the above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant