Open scott-huberty opened 1 month ago
@scott-huberty : Duplication of what I answered in #161
SPEC0 is a nice initiative. I did not know about it. In general, I favor the requirements being as flexible as possible to avoid creating dependency conflict in downstream projects but I am good with 1 too because this is a relatively young project so I think we need to keep the maintenance burden relatively low until there is more buy-in from the community.
Originally posted in https://github.com/lina-usc/pylossless/pull/161#issue-2423857408 :
Since v1.7 (April 2024), MNE uses edfio for writing EDF files. So we no longer should depend on edflib-python, but should use edfio.
There are a couple of ways we can go about this.
mne>=1.7
. This assures that people don't have an older version of MNE installed that will try to use edflib-python.<1.7
, check ifedflib-python
is installed. If it is>1.7
, check ifedfio
is installed, etc.Or I guess we could do a middle ground and continue to support mne v1.6, and thus add code to check if
edflib-python
oredfio
needs to be installed, as previously described.Personally I vote for 1, because I think the maintenance burden of 2 is currently too much for this project. Also, MNE only officially supports their latest stable release, so I don't want to support people using older versions that MNE doesn't even support themselves.
@Andesha @jadesjardins @christian-oreilly What do you think?