Skip to content

Unpin mypy dependency #6282

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

Closed
ricardoV94 opened this issue Nov 9, 2022 · 0 comments · Fixed by #6294
Closed

Unpin mypy dependency #6282

ricardoV94 opened this issue Nov 9, 2022 · 0 comments · Fixed by #6294

Comments

@ricardoV94
Copy link
Member

ricardoV94 commented Nov 9, 2022

Our pre-commit started failing with the latest release of mypy. I am temporarily pinning it in f66f320

We should unpin ASAP, which will involve fixing the new complaints from mypy.

michaelosthege added a commit that referenced this issue Nov 14, 2022
* Add a few missing type imports
* Trade assert with assignment to keep mypy happy
* Add a few type annotations
* Add missing return type for __call__
* Switch comment type declaration to raw
* Get operators.py to pass
* Fix pymc.backends.report
* Fix a bunch of typing issues
* Import __future__.annotations to fix "| None"
* Update pymc/step_methods/hmc/integration.py
* Add __future__.annotations to hmc.py
* Remove unused Any import
* Don't cast float to np.array
* Replace 0 with 0.0 for float zeros
* Update pymc/step_methods/hmc/nuts.py

Closes #6282

Co-authored-by: Adrian Seyboldt <[email protected]>
Co-authored-by: Michael Osthege <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant