Am 06.05.2015 um 20:58 schrieb Peter Brady:
Absolutely. I was thinking that there was a decently sized set of tests that were going to be run regularly without the cache in which case it might make sense to introduce another mark/option but if it's only a few than specifying them manually is probably better.
I'd definitely prefer a mark/decorator/whatever on the test itself. Keeps the information about the test in one place, instead of distributing it across the test code and the test driver.
We have more conditional testing like that BTW. Slow tests, Travis-only tests, tests that require numpy or matplotlib, etc. I'm starting to think that we should unify all these into a single decorator and let the test driver filter. Is something like that in Python's test.py? Then we should probably mimick that.
... right, see pytest.org/latest/example/markers.html . -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sympy. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/554A6934.6000107%40durchholz.org. For more options, visit https://groups.google.com/d/optout.
