Skip to content

Conversation

@SwayamInSync
Copy link
Member

closes #126

Here since for large inputs, argument reduction can lead to a very different values than float64 hence comparing the quadprecision agains mpmath with prec=113 instead of NumPy.

There are some cases where mpmath does not follow the IEEE standards, those cases are specifically handled

# See https://github.com/python/mypy/issues/18343#issuecomment-2571784915
def __new__(cls, /, value: _IntoQuad, backend: _Backend = "sleef") -> Self: ...

# Attributes
Copy link
Member Author

@SwayamInSync SwayamInSync Oct 26, 2025

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

Copy link
Contributor

@juntyr juntyr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@juntyr
Copy link
Contributor

juntyr commented Oct 27, 2025

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?

@SwayamInSync
Copy link
Member Author

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.

@SwayamInSync
Copy link
Member Author

Merging this in!

@SwayamInSync SwayamInSync merged commit 774c0eb into numpy:main Oct 27, 2025
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Inaccurate trignometric functions for "very" large/small inputs

2 participants