Skip to content

Changed the build backend and package management to hatchling and uv #100

Changed the build backend and package management to hatchling and uv

Changed the build backend and package management to hatchling and uv #100

Triggered via pull request October 28, 2024 20:21
Status Failure
Total duration 27s
Artifacts

python-app.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
Ruff (UP035): src/metametric/core/_ilp.py#L3
src/metametric/core/_ilp.py:3:1: UP035 Import from `collections.abc` instead: `Collection`, `Iterator`, `Sequence`
Ruff (UP035): src/metametric/core/_ilp.py#L3
src/metametric/core/_ilp.py:3:1: UP035 `typing.List` is deprecated, use `list` instead
Ruff (UP035): src/metametric/core/_ilp.py#L3
src/metametric/core/_ilp.py:3:1: UP035 `typing.Type` is deprecated, use `type` instead
Ruff (UP006): src/metametric/core/_ilp.py#L118
src/metametric/core/_ilp.py:118:10: UP006 Use `type` instead of `Type` for type annotation
Ruff (UP006): src/metametric/core/_ilp.py#L182
src/metametric/core/_ilp.py:182:27: UP006 Use `list` instead of `List` for type annotation
Ruff (UP006): src/metametric/core/_ilp.py#L218
src/metametric/core/_ilp.py:218:51: UP006 Use `type` instead of `Type` for type annotation
Ruff (UP035): src/metametric/core/_problem.py#L2
src/metametric/core/_problem.py:2:1: UP035 Import from `collections.abc` instead: `Sequence`, `Collection`
Ruff (UP035): src/metametric/core/_problem.py#L2
src/metametric/core/_problem.py:2:1: UP035 `typing.Tuple` is deprecated, use `tuple` instead
Ruff (UP006): src/metametric/core/_problem.py#L21
src/metametric/core/_problem.py:21:24: UP006 Use `tuple` instead of `Tuple` for type annotation
Ruff (UP006): src/metametric/core/_problem.py#L21
src/metametric/core/_problem.py:21:48: UP006 Use `tuple` instead of `Tuple` for type annotation
build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/