python-tuf/requirements/dev.txt

# Install tuf in editable mode and requirements for local testing with tox,
# and also for running test suite or individual tests manually.
# The build and tox versions specified here are also used as constraints
# during CI and CD Github workflows
-r build.txt
-r test.txt
-r lint.txt
-e .
Update requirements files comments Signed-off-by: Lukas Puehringer <lukas.puehringer@nyu.edu> Co-Authored-By: Joshua Lock <jlock@vmware.com> 2020-02-07 13:25:20 +00:00			`# Install tuf in editable mode and requirements for local testing with tox,`
build: Change build dependency pinning strategy * don't autoupgrade pip: let's consider pip to be part of platform? * pin build and tox in new requirements-build.txt: this mostly prevents tox from going to 4.x before we're ready * use requirements-build.txt as constraint when installing tox or build during CI & CD * use requirements-build.txt in requiremenets-dev.txt Note that coveralls is not pinned, not sure if it should be. Signed-off-by: Jussi Kukkonen <jkukkonen@google.com> 2022-12-09 15:12:34 +00:00			`# and also for running test suite or individual tests manually.`
			`# The build and tox versions specified here are also used as constraints`
			`# during CI and CD Github workflows`
build: shorten requirements file names Signed-off-by: Jussi Kukkonen <jkukkonen@google.com> 2023-02-06 11:18:19 +00:00			`-r build.txt`
			`-r test.txt`
			`-r lint.txt`
Restructure requirements files * Use suffixed instead of prefixed sub-requirements files to group them alphabetically in the file tree. * Layer requirements files akin to the in-toto project (see in-toto/in-toto#294). The hierarchy is: - requirements.in tuf runtime requirements, including optional requirements (pynacl and cyrptography) - requirements-pinned.txt pinned tuf runtime requirements, including optional and transitive (1 level deep) requirements and their hashes. The file is generated semi-automatically using pip-compile and a bash script (see document header), based off of requirements.in, combining requirements from all supported Python versions. This file should be auto-updated, by e.g. dependabot, and be used for ci/cd tests, to catch issues with new dependencies. - requirements-test.txt additional test runtime requirements - requirements-tox.txt combines requirements.txt, requirements-test.txt and additional test tools (for linting and coverage), i.e. everything that is needed in each tox environment to run the tests. - requirements-dev.txt lists tox for local development and testing, and also requirements-tox.txt and tuf in editable mode to run the test suite or individual tests directly. - requirements.txt requirements-pinned.txt with the hashes of the dependencies as reported by pip at the time of creating the file. NOTE: this is not used for testing or dev-install because pip doesn't allow mixed (with and without hashes) installations. This file should also be auto-updated, by e.g. dependabot. * Removes an obsolete version constraint on coverage Signed-off-by: Lukas Puehringer <lukas.puehringer@nyu.edu> 2020-02-06 12:14:24 +00:00			`-e .`