-
Notifications
You must be signed in to change notification settings - Fork 91
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
Broken: running individual python tests #45
Comments
Humm, yes, this cannot work, because we are doing a relative import ( We need that for python3 compat. I think the real answer of this issue is to have a real test runner instead of running them file by file. Do you want me to work on this? |
But aren't we using nose? You should be able to limit the ran tests to this file passing arguments to nose. |
@springmeyer |
Is this absolutely necessary for python3? Can't we support both 2 and 3 without breaking things? |
Yes, it's absolutely necessary for python3: there is not way any more to make false relative import (i.e. |
Correct. This is the way I run tests that I develop.
Correct, its not sufficient. Running that is slower, not easy to remember, and outputs of bunch of noise:
|
How much slower? :) I see
Humm, would a Makefile entry help? Like
I'll see how to fix that. |
Another problem @yohanboniface. But certain files, when run from the command line, are meant to print more debugging info. For example |
Also make test/python_tests/image_encoding_speed_test.py compliant with nosetest runner.
What about #53 ? :) |
Also make test/python_tests/image_encoding_speed_test.py compliant with nosetest runner.
Running individual test module like this works: cd test/
python -m python_tests.csv_test |
This used to work:
//cc @flippmoke @yohanboniface - any ideas?
The text was updated successfully, but these errors were encountered: