You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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:
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: