This rule detects the presence of unused variables in unpacked assignments.
See: https://docs.astral.sh/ruff/rules/unused-unpacked-variable/
Fixed automatically with : 'ruff check --select RUF059 --unsafe-fixes --fix' + one
manual fix in tests/test_e3/anod/context_test.py
Ref: it/org/software-supply-chain/production-pipeline/issues#204
This rule requests to remove the use encode (utf-8) as it is the default
python encoding. See https://docs.astral.sh/ruff/rules/unnecessary-encode-utf8/
Automatically fixed using 'ruff check --select UP012 --fix'
Ref: it/org/software-supply-chain/production-pipeline/issues#204
Using the root logger causes the messages to have no source information,
making them less useful for debugging.
for details see: https://docs.astral.sh/ruff/rules/root-logger-call/
The fix was done manually
Ref: it/org/software-supply-chain/production-pipeline/issues#204
This rule detects for the presence of unused arguments in lambda expression definitions.
for details see: https://docs.astral.sh/ruff/rules/unused-lambda-argument/
The fix was done manually
Ref: it/org/software-supply-chain/production-pipeline/issues#204
This rule requests to consider {expression} instead of concatenation, for
details see https://docs.astral.sh/ruff/rules/collection-literal-concatenation/
These fix was automatically made by ruff with the command:
'ruff check --select RUF005 --unsafe-fixes --fix'
but a manual change on src/e3/anod/store/__init__.py was needed to fix C409
flake8 rules
Ref: it/org/software-supply-chain/production-pipeline/issues#204
More third-party packages now provide type annotations or
stubs. Use those instead of configuring mypy to ignore
imports.
Fix mypy warning by updating annotations on e3.log to use tqdm types.
for it/e3-core#68
The argnames argument of pytest.mark.parametrize takes a string or a sequence of strings.
This MR fix case when multiple parameters are not passed using a tuple. These
fixes was made automatically by ruff.
See: https://docs.astral.sh/ruff/rules/pytest-parametrize-names-wrong-type/
Ref: it/org/software-supply-chain/production-pipeline/issues#193
This commit fix the Ruff rule UP032: https://docs.astral.sh/ruff/rules/f-string/
This is done automatically through ruff check --select UP032 --fix
Ref: it/org/software-supply-chain/production-pipeline/issues#193
This commit fix the Ruff rule ANN204: https://docs.astral.sh/ruff/rules/missing-return-type-special-method/
This done automatically for all file but 2 files needs manual action : tests/tests_e3/conftest.py and tests/tests_e3/json_test.py
Ref: it/org/software-supply-chain/production-pipeline/issues#193
When downloading a file from a store, if `self.downloaded_as` is a symlink
to our destination or vice versa, the copy will fail because the two files
are the same.
The previous implementation may lead us to think that we are protected for
such cases because we first compared if `os.path.abspath(source)` was
different from `os.path.abspath(destination)`, but that is not enough:
`os.path.abspath` doesn't follow symlinks, so the path returned could
differ, but still point to the same file on the system at the end.
To avoid this, the call to `os.path.abspath` has been replaced by
`Path(...).resolve()`, which will return an absolute path while following
symlinks.
