Am Mo., 3. Feb. 2025 um 18:45 Uhr schrieb Alois Schlögl < alois.schlo...@gmail.com>:
> [...] > Dear Matthias, > > > thanks for your offer to help. From my point of view, this would be > appreciated. > Please find below my assessment of the state of stimfit in debian: > > - It should be possible bring stimfit 0.16.4-1.1 into bookworm-backports > as is. > > - Concerning sid, this might be tricky because of the current dependency > on the old distutils. At this time, I'm not positive that I could do the > migration to numpy>=2 and the new distutils within the time frame of the > release of trixie. If you know how to address this, your contribution is > most welcome. > Oh wow, this is a lot more than I expected, and that also explains why the package isn't in unstable yet... I can have a look though! - What is possible is disabling the embedded python (using "./configure > --disable-python ..."). That's what we call "stimfit-lite" on the > project homepage https://github.com/neurodroid/stimfit . What I can > offer is preparing an upload for a stimfit-lite (w/o python support) for > Debian. > - This would mean that the debian package "python3-stfio" would not be > available. Some of its functionality could be replaced by python3-biosig > <https://packages.debian.org/unstable/python3-biosig> . [1] provides > some starting points how to do this. However, full compatibility is not > available at this time. > Our lab uses python3-stfio specifically to load CED binary CFS files, which as far as I know can't be reliably done with any other tool. So, it would be neat to keep that support. Migrating Python build systems is just about the least fun thing I can imagine, but the Numpy transition might not be too bad depending on how stimfit uses it (I have done that in a different project and it was simple, however, usage of the API was also fairly basic there). I'll have a look... Best, Matthias -- I welcome VSRE emails. See http://vsre.info/
