-
Notifications
You must be signed in to change notification settings - Fork 90
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
bidspath example contains runtimewarning #829
Comments
Shall we finally kill off all the BIDSPath "trying to guess what the user meant" magic? :) |
Closed
yes 💯 Let's do it in 0.9 🙏 |
sappelhoff
added a commit
to sappelhoff/mne-bids
that referenced
this issue
Jul 13, 2021
6 tasks
hoechenberger
pushed a commit
that referenced
this issue
Jul 14, 2021
* fix doctests in path.py * test: use pytest --doctest-modules * fix some more examples * make use of _write_json instead of json.dump * fix fine-calib and crosstalk doctest * DATA: add tiny_bids test dataset ~800kb * fix all doctests using new test ds * add code for generating tiny_bids * fix example, sphinx warning * use tiny_bids in bidspath example, fix #829 * write TSV files with newline character * add missing newlines at end of files * do not run pytest on examples we did not do that before either, but --doctest-modules is now ON and that option apparently also runs the examples * add whatsnew for TSV line end * properly ignore examples in pytest * fix head_to_mri upstream API change * xfail doctest on windows due to / vs \ * BIDSPath __str__ always .as_posix() * fix op.join -> Path * root in __repr__ --> posix path or None * circumvent bids_path.root __str__ * 1) fix pep, 2) fix type hints, 3) fix example ds * fix type hint * I should run make pep before pushing
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://mne.tools/mne-bids/dev/auto_examples/bidspath.html#bidspath-example
and there are 2 more of those. At least it should be discussed in the example why there is such a warning.
The text was updated successfully, but these errors were encountered: