TST: filter ImportWarnings in NoseTester. #251
Conversation
Warnings show up when a directory with the same name as a Python file or compiled extension is seen which doesn't have an __init__.py file in it. This situation is very common, for example in SciPy where many extensions are created from source files located under a directory with the same name. This filter is located within a context manager, so only filters when running tests.
|
Looks good to me. |
|
Are any of the warning potentially useful? |
|
None of the ones I'm seeing. I can't imagine a case where they would be useful. |
|
They're all like this: A bit braindead, Python should simply recognize that when there's a successful import of |
|
OK. In it goes. |
TST: filter ImportWarnings in NoseTester.
|
Oops, ImportWarning is new in 2.5, not available in 2.4. How do you want to deal with that? |
|
Hmm, sloppy. It should have been a bare |
|
And again replying to fast. I read it as |
|
I put up pull request 253 with this and some rearrangement. |
feat Add vshl[q]_n_[s8|s16|s32|s64|u8|u16|u32|u64]
Warnings show up when a directory with the same name as a Python file or
compiled extension is seen which doesn't have an init.py file in it. This
situation is very common, for example in SciPy where many extensions are
created from source files located under a directory with the same name.
This filter is located within a context manager, so only filters when running
tests.
See thread http://mail.python.org/pipermail/python-dev/2006-June/066364.html for history.