[pre-commit.ci] pre-commit automatically updated. #253
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![pre-commit-ci[bot]](https://avatars.githubusercontent.com/in/68672?s=60&v=4){kind=small}
updates: - [github.com/astral-sh/ruff-pre-commit: v0.1.9 → v0.1.11](astral-sh/ruff-pre-commit@v0.1.9...v0.1.11) - [github.com/pre-commit/mirrors-eslint: v8.56.0 → v9.0.0-alpha.0](pre-commit/mirrors-eslint@v8.56.0...v9.0.0-alpha.0)
pre-commit-ci
bot
force-pushed
the
pre-commit-ci-update-config
branch
from
98c81f2
to
17db13d
Compare
ns-rse
pushed a commit
that referenced
this pull request
Jan 10, 2024
New releases of `pytest-regtest>=2.0.0` on PyPI are currently broken as the released packages don't appear to include the Python code for the module itself. This has been reported upstream and when fixed I will remove the dependency. + [pytest-regtest #20](https://gitlab.com/uweschmitt/pytest-regtest/-/issues/20) At the same time I've... + Made the `pre-commit` updates that were automated in #253 where the `pytest-regtest` issue cropped up + Added `no-commit-to-branch` check to `pre-commit` hooks which protects against commits to `master` locally. + Introduced `NPY201` checks under `ruff` linting to check for forthcoming Numpy2 deprecations. Numpy2 is due to be released early later this year (first release candidate is scheduled 2024-02-01). This may introduce some breaking changes, a broad overview is available [here](https://pythonspeed.com/articles/numpy-2/). 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). The official [NumPy 2.0 migration guide — NumPy v2.0.dev0 Manual](https://numpy.org/devdocs/numpy_2_0_migration_guide.html) suggests that `ruff` can be leveraged to address the mentioned changes under [Ruff Plugin](https://numpy.org/devdocs/numpy_2_0_migration_guide.html#ruff-plugin). A useful summary of how to handle potential problems is provided at [Numpy #24300](numpy/numpy#24300) and broadly suggests pinning `numpy<2.0` for releases whilst development proceeds on resolving issues.
|
Updates applied via #255 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
updates: