mbedtls/scripts/ci.requirements.txt

# Python package requirements for Mbed TLS testing.

-r driver.requirements.txt

# 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.
pylint == 2.4.4

# Use the earliest version of mypy that works with our code base.
# See https://github.com/Mbed-TLS/mbedtls/pull/3953 .
mypy >= 0.780

# Install cryptography to avoid import-error reported by pylint.
# What we really need is cryptography >= 35.0.0, which is only
# available for Python >= 3.6.
cryptography # >= 35.0.0
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 18:13:34 +00: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 18:17:03 +00:00			`-r driver.requirements.txt`

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 18:13:34 +00: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.`
			`pylint == 2.4.4`

			`# Use the earliest version of mypy that works with our code base.`
Update references to old Github organisation Replace references to ARMmbed organisation with the new org, Mbed-TLS, following project migration. Signed-off-by: Dave Rodgman <dave.rodgman@arm.com> 2022-03-31 13:07:01 +00:00			`# See https://github.com/Mbed-TLS/mbedtls/pull/3953 .`
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 18:13:34 +00:00			`mypy >= 0.780`
cert_audit: Check the version of cryptography The script requires cryptography >= 35.0.0, we need to check the version and provide meaningful error message when the package version was too old. Signed-off-by: Pengyu Lv <pengyu.lv@arm.com> 2023-04-25 06:55:38 +00:00
			`# Install cryptography to avoid import-error reported by pylint.`
			`# What we really need is cryptography >= 35.0.0, which is only`
			`# available for Python >= 3.6.`
Revert "Install cryptography only on linux platform" This reverts commit eb2c39ed2bc6a126ae7bdb6eab0457ebd6a32cfc. We temporarily turned off the cryptography requirement on Windows due to a CI instance that had an old, incompatible verison of pip. That CI instance has been upgraded so we no longer need the workaround. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com> 2023-06-16 15:05:22 +00:00			`cryptography # >= 35.0.0`