TeamHepta/mbedtls
1
0
Fork 0
mirror of https://github.com/Mbed-TLS/mbedtls.git synced 2026-04-18 18:08:46 +02:00
Code Issues Packages Projects Releases Wiki Activity
Files
bb5cfbbdec43242901fe8a9d74291ed3300a622c
mbedtls/scripts/ci.requirements.txt

26 lines
1.0 KiB
Plaintext
Raw Normal View History

Declare which Python packages we use Add pip requirements files. We'll have separate requirements files for different target audiences. Each file can use `-r` lines to include other files. This commit adds two requirement files: one with everything that's needed to pass the CI, and one with additional tools that are suggested for Mbed TLS maintainers to install locally. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2021-11-17 19:13:34 +01:00
# Python package requirements for Mbed TLS testing.
Add requirement on Jinja to integrate drivers Driver implementers need to regenerate wrappers. This will use Jinja2 as discussed in https://github.com/ARMmbed/mbedtls/pull/5067#discussion_r738794607 On the development branch, driver integration is always needed to generate the driver wrapper and thus to build the library, so this requirement applies to everyone, not just driver implementers. In releases, we plan to include a default driver wrapper with support for basic use cases only, meaning that the line `-r driver.requirements.txt` should be removed from `basic.requirements.txt` in releases. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2021-11-17 19:17:03 +01:00
-r driver.requirements.txt
Move requirements to the framework for scripts in the framework Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2026-02-26 19:35:56 +01:00
-r ../framework/scripts/ci.requirements.txt
Add requirement on Jinja to integrate drivers Driver implementers need to regenerate wrappers. This will use Jinja2 as discussed in https://github.com/ARMmbed/mbedtls/pull/5067#discussion_r738794607 On the development branch, driver integration is always needed to generate the driver wrapper and thus to build the library, so this requirement applies to everyone, not just driver implementers. In releases, we plan to include a default driver wrapper with support for basic use cases only, meaning that the line `-r driver.requirements.txt` should be removed from `basic.requirements.txt` in releases. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2021-11-17 19:17:03 +01:00
Restrict CI-specific python requirements to Linux The dependencies declared in ci.requirements.txt are only used in scripts that we run on the Linux CI. Signed-off-by: Bence Szépkúti <bence.szepkuti@arm.com>
2025-07-16 14:18:12 +02:00
# The dependencies below are only used in scripts that we run on the Linux CI.
Declare which Python packages we use Add pip requirements files. We'll have separate requirements files for different target audiences. Each file can use `-r` lines to include other files. This commit adds two requirement files: one with everything that's needed to pass the CI, and one with additional tools that are suggested for Mbed TLS maintainers to install locally. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2021-11-17 19:13:34 +01:00
# Use a known version of Pylint, because new versions tend to add warnings
# that could start rejecting our code.
# 2.4.4 is the version in Ubuntu 20.04. It supports Python >=3.5.
Restrict CI-specific python requirements to Linux The dependencies declared in ci.requirements.txt are only used in scripts that we run on the Linux CI. Signed-off-by: Bence Szépkúti <bence.szepkuti@arm.com>
2025-07-16 14:18:12 +02:00
pylint == 2.4.4; platform_system == 'Linux'
Declare which Python packages we use Add pip requirements files. We'll have separate requirements files for different target audiences. Each file can use `-r` lines to include other files. This commit adds two requirement files: one with everything that's needed to pass the CI, and one with additional tools that are suggested for Mbed TLS maintainers to install locally. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2021-11-17 19:13:34 +01:00
Downgrade mypy to a version that works with our code base mypy >=0.960 rejects macro_collector.py. https://github.com/Mbed-TLS/mbedtls-framework/issues/50 We currently need mypy >=0.940, <0.960. Pick 0.942, which works, and is the system version on Ubuntu 22.04. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2024-09-23 19:16:47 +02:00
# Use a version of mypy that is compatible with our code base.
# mypy <0.940 is known not to work: see commit
# :/Upgrade mypy to the last version supporting Python 3.6
# mypy >=0.960 is known not to work:
# https://github.com/Mbed-TLS/mbedtls-framework/issues/50
# mypy 0.942 is the version in Ubuntu 22.04.
Restrict CI-specific python requirements to Linux The dependencies declared in ci.requirements.txt are only used in scripts that we run on the Linux CI. Signed-off-by: Bence Szépkúti <bence.szepkuti@arm.com>
2025-07-16 14:18:12 +02:00
mypy == 0.942; platform_system == 'Linux'
Add Python requirements from framework/util Any `all.sh` component that runs a script that requires a more recent version of Python must have a `support_xxx` function that checks for the requisite Python version or package. At this time, there is no such requirement yet in the mbedtls repository. The directory `framework/util` is not yet checked by `pylint` or `mypy`, because we use older versions of these tools that don't work well with modern Python versions. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2026-02-11 18:16:13 +01:00
# More requirements for scripts in the framework that might not work in
# older versions of Python. Note that requirements that are not available
# in the oldest version of Python on our CI must be annodated with
# "python >= ...".
-r ../framework/util/requirements.txt
Reference in New Issue Copy Permalink