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
Currently, eyelinkIO will read stimulus events ("messages" in EyeLink terminology) from the EDF file and store them as byte strings (see example below). This was inherited from the original implementation in the pyeparse package.
After a chat with @teonbrooks we've concluded that we should probably just store these as regular ol' Python strings, because 1) It will make working with these events easier for user, 2) We don't need to be Python 2 compatible, and 3) I don't think memory is an issue that warrants the use of byte strings.
Currently, eyelinkIO will read stimulus events ("messages" in EyeLink terminology) from the EDF file and store them as byte strings (see example below). This was inherited from the original implementation in the pyeparse package.
After a chat with @teonbrooks we've concluded that we should probably just store these as regular ol' Python strings, because 1) It will make working with these events easier for user, 2) We don't need to be Python 2 compatible, and 3) I don't think memory is an issue that warrants the use of byte strings.
I think that changing this line:
eyelinkio/src/eyelinkio/edf/read.py
Lines 197 to 198 in c3afb9a
to this should work:
Which will specify a Unicode string type while preserving the
_MAX_MSG_LEN
constraint that currently exists.Example of current behavior
The text was updated successfully, but these errors were encountered: