Explain the story about cryptography version requirements
Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
This commit is contained in:
parent
dc23236f0a
commit
7990a3296d
1 changed files with 6 additions and 3 deletions
|
@ -11,7 +11,10 @@ pylint == 2.4.4
|
||||||
# See https://github.com/Mbed-TLS/mbedtls/pull/3953 .
|
# See https://github.com/Mbed-TLS/mbedtls/pull/3953 .
|
||||||
mypy >= 0.780
|
mypy >= 0.780
|
||||||
|
|
||||||
# Install cryptography to avoid import-error reported by pylint.
|
# At the time of writing, only needed for tests/scripts/audit-validity-dates.py.
|
||||||
# What we really need is cryptography >= 35.0.0, which is only
|
# It needs >=35.0.0 for correct operation, and that requires Python >=3.6,
|
||||||
# available for Python >= 3.6.
|
# but our CI has Python 3.5. So let pip install the newest version that's
|
||||||
|
# compatible with the running Python: this way we get something good enough
|
||||||
|
# for mypy and pylint under Python 3.5, and we also get something good enough
|
||||||
|
# to run audit-validity-dates.py on Python >=3.6.
|
||||||
cryptography # >= 35.0.0
|
cryptography # >= 35.0.0
|
||||||
|
|
Loading…
Reference in a new issue