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
Type fixes for Pint >= 0.19.3 and attrs fixes for Python 3.11. #25
Conversation
Codecov Report
@@ Coverage Diff @@
## main #25 +/- ##
==========================================
+ Coverage 73.16% 73.91% +0.74%
==========================================
Files 14 14
Lines 1994 1997 +3
==========================================
+ Hits 1459 1476 +17
+ Misses 535 521 -14
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
15e56f5
to
a347516
Compare
I actually can't find documentation for |
In general the pint API seems incomplete: https://pint.readthedocs.io/en/stable/api/specific.html For instance, there's another module pint.testing, but I don't see it mentioned in the link above. Is that site out of date and their real documentation is elsewhere? |
This is confusing overall. After discussion on the pint issue, I've mostly switched back to Quantity instead of PlainQuantity, except where it is actually needed for mypy to stop complaining. PlainQuantity appears to be a new addition that isn't supposed to usually be necessary, but in adding it, the generic for the magnitude type for Quantity was removed. I'm hoping that will be added back at some point. |
See:
python-attrs/attrs#969
hgrecco/pint#1642