|
2 | 2 |
|
3 | 3 | -r driver.requirements.txt |
4 | 4 |
|
| 5 | +# The dependencies below are only used in scripts that we run on the Linux CI. |
| 6 | + |
5 | 7 | # Use a known version of Pylint, because new versions tend to add warnings |
6 | 8 | # that could start rejecting our code. |
7 | 9 | # 2.4.4 is the version in Ubuntu 20.04. It supports Python >=3.5. |
8 | | -pylint == 2.4.4 |
| 10 | +pylint == 2.4.4; platform_system == 'Linux' |
9 | 11 |
|
10 | 12 | # Use a version of mypy that is compatible with our code base. |
11 | 13 | # mypy <0.940 is known not to work: see commit |
12 | 14 | # :/Upgrade mypy to the last version supporting Python 3.6 |
13 | 15 | # mypy >=0.960 is known not to work: |
14 | 16 | # https://github.com/Mbed-TLS/mbedtls-framework/issues/50 |
15 | 17 | # mypy 0.942 is the version in Ubuntu 22.04. |
16 | | -mypy == 0.942 |
| 18 | +mypy == 0.942; platform_system == 'Linux' |
17 | 19 |
|
18 | 20 | # At the time of writing, only needed for tests/scripts/audit-validity-dates.py. |
19 | | -# It needs >=35.0.0 for correct operation, and that requires Python >=3.6, |
20 | | -# but our CI has Python 3.5. So let pip install the newest version that's |
21 | | -# compatible with the running Python: this way we get something good enough |
22 | | -# for mypy and pylint under Python 3.5, and we also get something good enough |
23 | | -# to run audit-validity-dates.py on Python >=3.6. |
24 | | -cryptography # >= 35.0.0 |
| 21 | +# It needs >=35.0.0 for correct operation, and that requires Python >=3.6. |
| 22 | +# >=35.0.0 also requires Rust to build from source, which we are forced to do on |
| 23 | +# FreeBSD, since PyPI doesn't carry binary wheels for the BSDs. |
| 24 | +cryptography >= 35.0.0; platform_system == 'Linux' |
25 | 25 |
|
26 | 26 | # For building `framework/data_files/server9-bad-saltlen.crt` and check python |
27 | 27 | # files. |
28 | | -asn1crypto |
| 28 | +asn1crypto; platform_system == 'Linux' |
0 commit comments