[python] fix mypy error with pycryptodome 4.4
TI
2d ago+40+40+01234567890123456789-32-32-01234567890123456789
pycryptodome 4.4 types DSS.new(mode=...) as a Literal, which breaks mypy in all python sample CI jobs.
PR checklist
- Read the contribution guidelines.
- Run the following to build the project and update samples:
(For Windows users, please run the script in WSL)./mvnw clean package || exit ./bin/generate-samples.sh ./bin/configs/*.yaml || exit ./bin/utils/export_docs_generators.sh || exit
Commit all changed files.
This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
These must match the expectations made by your contribution.
You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example./bin/generate-samples.sh bin/configs/java*.
IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed. - If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.
Summary by cubic
Fixes a mypy error in the Python client signing code caused by pycryptodome 4.4, which types DSS.new(mode=...) as a Literal. The generated signing template now annotates the ECDSA mode constants with Final and casts the mode argument when calling DSS.new, with the cast kept within the flake8 line length limit.