-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
filterwarnings #229
Comments
>>> import warnings
>>> warnings.warn('warning')
__main__:1: UserWarning: warning
>>> import quantecon
>>> warnings.warn('warning')
>>> |
We should definitely not be silencing all warnings. I haven't looked, but do we know why we are even expecting to have warnings in arma.py? |
Comment in # == Ignore unnecessary warnings concerning casting complex variables back to
# floats == # |
Comment in # == Suppress warnings from checking conditioning of matrices == # |
I propose we remove the |
mmcky
added a commit
that referenced
this issue
Feb 25, 2016
Closing this issue as discussion has moved to PR #231 |
mmcky
added a commit
that referenced
this issue
Nov 10, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems that once
quantecon
is imported, the warnings the user issues bywarnings.warn
are ignored, probably because ofwarnings.filterwarnings('ignore')
in arma.py (and there is alsowarnings.simplefilter("ignore", RuntimeWarning)
in matrix_eqn.py).If it is indeed the case, this is problematic. Is there any way to put
warnings.simplefilter
in a "local scope"?The text was updated successfully, but these errors were encountered: