-
Notifications
You must be signed in to change notification settings - Fork 73
TST: adding marker and stricter warning checks #214
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
Nice, only warning made error is |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The stricter warnings check may be worth adding, although having to silence warnings triggered by the Python standard library is very ugly. The test marking much less so, IMO.
dea588e
to
00ad964
Compare
Made changes, and updated history to be one commit per change. Also updated tmpdir to tmppath, since I noticed that elsewhere being |
f16135b
to
e8c6ca4
Compare
2e2e897
to
a6a8399
Compare
a6a8399
to
0d08689
Compare
Signed-off-by: Henry Schreiner <henryschreineriii@gmail.com> fixup
Signed-off-by: Henry Schreiner <henryschreineriii@gmail.com>
Signed-off-by: Henry Schreiner <henryschreineriii@gmail.com>
The former returns a pathlib.Path, the latter a py.path. Signed-off-by: Henry Schreiner <henryschreineriii@gmail.com>
0d08689
to
31012f4
Compare
Adding a marker for the isolated build testing. You can turn off this with
-m "not isolated"
- might be useful for conda-forge, where isolated builds don't matter.Making the tests a bit stricter, checking for warnings.