-
-
Notifications
You must be signed in to change notification settings - Fork 10.9k
BUG: Make numpy import when run with Python flag '-OO'. #5149
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
Conversation
This consists of checking for a docstring equal to None and skipping two tests that require docstrings. Closes numpy#5148.
Looks reasonable to me. Should we add a travis run with |
@njsmith I thought about it... Adding commit to test that. |
Thanks a lot, everyone! |
I think that flag is to exotic for a new travis test, how about adding it to the separate compilation test? |
LGTM. I don't really care where the flag goes in the travis configuration, just so long as we have some automatic test so we never have to waste brain cells thinking about Even just adding |
868a039
to
43ca904
Compare
@juliantaylor Done. We probably only need one separate compilation test and one relaxed stride test, but that is for another time... |
BUG: Make numpy import when run with Python flag '-OO
BUG: Make numpy import when run with Python flag '-OO
thanks merged |
This consists of checking for a docstring equal to None and skipping two
tests that require docstrings.
Closes #5148.
Rebased for backport to 1.9.