yuzu-emu/mbedtls
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
mbedtls/scripts/driver.requirements.txt

17 lines
616 B
Text
Raw Normal View History

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
# Python package requirements for driver implementers.
Require an older version of markupsafe for the sake of older Jinja2 Jinja2 <3.0 require markupsafe <2.1.0, but does not declare this requirement. (Jinja2 2.x has not been updated since markupsafe 2.1.0 came out). So declare this requirement ourselves. This is not ideal, since we would want to use the latest markupsafe with the latest Jinja2. But at least it gives us a consistent set of versions to run the CI with. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2022-02-19 20:28:21 +01:00
# Jinja2 <3.0 needs an older version of markupsafe, but does not
# declare it.
# https://github.com/pallets/markupsafe/issues/282
# https://github.com/pallets/jinja/issues/1585
markupsafe < 2.1
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
# Use the version of Jinja that's in Ubuntu 20.04.
# See https://github.com/ARMmbed/mbedtls/pull/5067#discussion_r738794607 .
Clarify comment Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2021-12-02 12:48:50 +01:00
# Note that Jinja 3.0 drops support for Python 3.5, so we need to support
# Jinja 2.x as long as we're still using Python 3.5 anywhere.
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
Jinja2 >= 2.10.1
Require an older version of markupsafe for the sake of older Jinja2 Jinja2 <3.0 require markupsafe <2.1.0, but does not declare this requirement. (Jinja2 2.x has not been updated since markupsafe 2.1.0 came out). So declare this requirement ourselves. This is not ideal, since we would want to use the latest markupsafe with the latest Jinja2. But at least it gives us a consistent set of versions to run the CI with. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2022-02-19 20:28:21 +01:00
# Jinja2 >=2.10, <3.0 needs a separate package for type annotations
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
types-Jinja2
Reference in a new issue Copy permalink