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
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 rules is to detect function without return annotation, most of
them was fixed automatically by ruff, 19 was done manually
Ref: it/org/software-supply-chain/production-pipeline/issues#193
To workaround the fact that we don't have network access when running
`pip wheel` we can pass the argument `--no-build-isolation` and have
`the tool retrieve the build dependency from the current environment.
It's a good idea to also pass `--no-index` to ensure that the tests
won't try to access the PyPI server.
for it/e3-core#15
Previous approach was using a naive algorithm that was failing to
resolve complex constraints, mainly because of the absence of
backtracking. In order to solve properly the issue, the new
implementation drags the generic constraint solver used by pip
(resolvelib) and instantiate it.
Note also that the package now only depends on the standard
PyPI simple API rather than the release obsolete one.
The pypi simulator is used to simulate the interactions between our code
and the real pypi.
Addresses are mocked, and for the moment it only simulates requests in
https://pypi.org/pypi/<YOUR PACKAGE>/json format.
Test json metadata must be downloaded in advance and placed in
tests/tests_e3/pypi_data/json.
Related to #671
Some packages like google-api-client can have requirements that discard
all micro versions of a package for a given major and minor version.
This is the case of the google-api-client package (v 2.97) which for
example requires google-api-core!=2.1.*.
