-
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
Potential incompatibility between MNE 1.8.0 and MNE-BIDS 0.15.0 #1306
Comments
Hello! 👋 Thanks for opening your first issue here! ❤️ We will try to get back to you soon. 🚴🏽♂️ |
Thanks for the report! You are right -- we should probably make a release to fix this. |
Thanks for your work on this really nice tool! I would support the fix for this bug being a patch to the current version (e.g. 0.15.1) rather than part of the next minor version milestone, provided the team has the resources to do so. It is currently breaking the |
Hey all, I will try to push out a release this Saturday! |
Thanks! I've also found the problem in the upstream repo for MNE and created another issue for that so hopefully it will be fixed at the source as well soon. |
@bootstrapbill @berkgercek @thht mne-bids v0.16.0 has been released and is available on PyPI and in a few hours on conda-forge! 🚀 happy bids-ifying! |
Description of the problem
When calling write_raw_bids() I ran into the following error:
TypeError: 'datetime.date' object is not subscriptable
After some digging I realised that this is due to the switch in MNE 1.8.0 to storing subject birthdays as a date object instead of a tuple. But, in MNE-BIDS 0.15.0 a tuple is still expected.
I can see this bug has already been fixed here: #1278 (comment), but since that's currently only in the development version the latest stable releases of MNE and MNE-BIDS are incompatible (at least in this specific situation), right?
Steps to reproduce
Expected results
Expect write_raw_bids() to run as normal.
Actual results
TypeError: 'datetime.date' object is not subscriptable
Additional information
I'm not sure what the protocol is here, can the fix be backported? Or could this potential incompatibility be flagged in the documentation until the next release is rolled out? I've checked and the issue can easily be circumvented by either downgrading MNE (to 1.7.1) or installing the current development version of MNE-BIDS, so one of those solutions could be recommended?
The text was updated successfully, but these errors were encountered: