While attempting to check forward compatibility with CPython 3.15 (mostly to see what fails to build), I noticed that scikit-image was declared as a direct dependency, yet the only place I see it explicitly imported (under skimage) is in a test module, and even there it's just used to check for its version number1. It's not a transitive dependency to anything else in the requirements either, so I'm wondering if this maybe is a zombie dependency that should simply be removed ?
While attempting to check forward compatibility with CPython 3.15 (mostly to see what fails to build), I noticed that
scikit-imagewas declared as a direct dependency, yet the only place I see it explicitly imported (underskimage) is in a test module, and even there it's just used to check for its version number1. It's not a transitive dependency to anything else in the requirements either, so I'm wondering if this maybe is a zombie dependency that should simply be removed ?Footnotes
btw, the version number check uses straight
strcomparison, which is almost certainly not what you want ('0.10' > '0.2' is False) ↩