EDIT June 2021: Surprised this is still getting votes. If at all possible, consider using ptyest with the –last-failed option. It turns out this is trivial with nose. First run the command and include the –with-id flag. # Environment stuff deleted nosetests python/*Tests.py -v –with-id nosetests python/*Tests.py -v –failed If, say, four tests fail, running … Read more
For the string variable a, the only solution is global a. If you look at the Python 2 and Python 3 source code, setupModule() doesn’t appear to do anything magical, so all the usual namespace rules apply. If a were a mutable variable, like a list, you could define it at global scope and then … Read more
2.0 Update (10/8/19) Setting TF_CPP_MIN_LOG_LEVEL should still work (see below in v0.12+ update), but there is currently an issue open (see issue #31870). If setting TF_CPP_MIN_LOG_LEVEL does not work for you (again, see below), try doing the following to set the log level: import tensorflow as tf tf.get_logger().setLevel(‘INFO’) In addition, please see the documentation on … Read more
I got this problem until I setup nose with sudo: sudo pip install nose
nose provides tools for testing exceptions (like unittest does). Try this example (and read about the other tools at Nose Testing Tools from nose.tools import * l = [] d = dict() @raises(Exception) def test_Exception1(): ”’this test should pass”’ l.pop() @raises(KeyError) def test_Exception2(): ”’this test should pass”’ d[1] @raises(KeyError) def test_Exception3(): ”’this test should fail … Read more
Version 0.11.1 is currently available. You can get a list of tests without running them as follows: nosetests -v –collect-only
This is happening due to a version incompatibility between numpy and scipy. numpy in its latest versions have deprecated numpy.testing.nosetester. Replicating the issue pip install numpy==1.18 # > 1.18 pip install scipy<=0.19.0 # <= 0.19 and from sklearn.tree import DecisionTreeClassifier as DTC Triggers the error. Fixing the error Upgrade your scipy to a higher version. … Read more
You need to have a copy of nose installed in the virtual environment. In order to force installation of nose into the virtualenv, even though it is already installed in the global site-packages, run pip install with the -I flag: (env1)$ pip install nose -I From then on you can just run nosetests as usual.
Use entr: $ brew install entr $ find . -name ‘*.py’ | entr python ./manage.py test Or, for extra credit, combine it with ack: $ ack –python | entr python ./manage.py test If you want it to even find new files as you add them: $ until ack -f –python | entr -d python ./manage.py … Read more
The other thing which always gets me with nose is that it won’t run tests in executable files. I’m not exactly sure why that would make a difference across Mac/Ubuntu, but it’s worth a shot. Make sure that the scripts didn’t somehow get chmod +x‘d on the Mac… And if they did, fix them with … Read more