-
-
Couldn't load subscription status.
- Fork 13
TEST: Trignometric ufunc tests #211
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
Conversation
| # See https://github.com/python/mypy/issues/18343#issuecomment-2571784915 | ||
| def __new__(cls, /, value: _IntoQuad, backend: _Backend = "sleef") -> Self: ... | ||
|
|
||
| # Attributes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These new attributes aren't added in stubs for the PR #208 , small addition do did in this PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
Once we merge this PR, it would be good to issue another release, e.g. v0.3, so that it is easier to test the new functionality and find any other issues that we want to resolve before a v1.0 release. @ngoldbaum When will numpy v2.4 be released, which (correct me if I'm wrong) we now depend on for the improved dtype and finfo support? |
|
Yeah we decided to make a release, I am backporting some independent features from the NumPy 2.4 to another branch and then do the release. |
|
Merging this in! |
closes #126
Here since for large inputs, argument reduction can lead to a very different values than
float64hence comparing the quadprecision againsmpmathwithprec=113instead of NumPy.There are some cases where mpmath does not follow the IEEE standards, those cases are specifically handled