-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Annotate hash module #970
base: main
Are you sure you want to change the base?
Annotate hash module #970
Conversation
This PR is not just about hash module, right? Also, what's missing for marking this ready for review? |
yeah there's refactor (and tightening) of mypy config and minor annotation fixes that result from that
possibly just fixing the PR message? |
* Move config to pyproject.toml * Turn on useful mypy options * Don't check tests with mypy: too much to fix right now * Add py.typed to announce this project is type annotated * Fix various annotation issues Issues remain in hash module Signed-off-by: Jussi Kukkonen <[email protected]>
It's not really possible to annotate hash correctly but let's do something... Signed-off-by: Jussi Kukkonen <[email protected]>
This is useful since it will notice use of too new futures (or lack of "from __future__ import annotations"). Signed-off-by: Jussi Kukkonen <[email protected]>
Only change in this force-push is that |
I'd like to statically analyze calls to securesystemslib in other projects
Changelog:
hashlib.blake2b()
instead of hashlib.new() for the 256bit blake2bFileSystemBackend.__new__()
: theoretically an API change but I don't thinkobject.__new__()
takes extra args so I doubt it was ever used.