We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
pyright seems to be faster, more comprehensive, and less buggy.
We might be able to eliminate some annotations and guards that we added (e.g. to credere-backend) to get mypy to pass.
We might need to keep mypy where plugins are relevant (if used with Django, apparently).
If switching, rename workflows to types.yml
Not sure if there is an advantage to using mypy in combination with mypyc (e.g. if there are shared assumptions of behavior) re: #113
In any case, we should document how to set up whichever tool, e.g.:
[tool.mypy] strict = true warn_unreachable = true exclude = "(build|docs|tests)/"
- repo: https://github.com/pre-commit/mirrors-mypy rev: v1.12.0 hooks: - id: mypy exclude: "(docs|tests)/" additional_dependencies: - types-orjson - types-pika
The text was updated successfully, but these errors were encountered:
No branches or pull requests
pyright seems to be faster, more comprehensive, and less buggy.
We might be able to eliminate some annotations and guards that we added (e.g. to credere-backend) to get mypy to pass.
We might need to keep mypy where plugins are relevant (if used with Django, apparently).
If switching, rename workflows to types.yml
Not sure if there is an advantage to using mypy in combination with mypyc (e.g. if there are shared assumptions of behavior) re: #113
In any case, we should document how to set up whichever tool, e.g.:
The text was updated successfully, but these errors were encountered: