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
Numpy2 is due to be released later this year (first release candidate is scheduled 2024-02-01).
This may introduce some breaking changes, a broad overview is available here.
Mentioned in that article is that scikit-image has issues, which is indirect because the package has an optional dependency on matplotlib (I've discovered this whilst working on skan issues).
Although I've tried this on another project and pre-commit complained that tool.ruff.lint was a duplicate (I think because I have other tool.ruff.lint.* sections already defined). What worked for me was adding the following...
Numpy2 is due to be released later this year (first release candidate is scheduled 2024-02-01).
This may introduce some breaking changes, a broad overview is available here.
Mentioned in that article is that
scikit-image
has issues, which is indirect because the package has an optional dependency onmatplotlib
(I've discovered this whilst working onskan
issues).The official NumPy 2.0 migration guide — NumPy v2.0.dev0 Manual suggests that
ruff
can be leveraged to address the mentioned changes under Ruff Plugin.To which end we may be able to check and anticipate any breaking changes by adding the following to
pyproject.toml
:Although I've tried this on another project and
pre-commit
complained thattool.ruff.lint
was a duplicate (I think because I have othertool.ruff.lint.*
sections already defined). What worked for me was adding the following...After adding this the checks should be run using the
pre-commit
hookThe text was updated successfully, but these errors were encountered: