Fix arb powers with integer exponents - #427
Open
morluto wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #426.
arb.__pow__currently converts Python and FLINT integer exponents toarbbefore dispatching to genericarb_pow. For an interval crossing zero, that path can returnnaneven for exponents such as 1 and 2.This change preserves the exponent type and calls FLINT's integer-specific
arb_pow_fmpzfor Pythonintandfmpzoperands. Other supported exponent types continue to usearb_powas before. Regression coverage checks that zero-crossing interval powers remain finite and enclose representative values.Validation:
spin test -- --pyargs flint.test.test_arb -q(47 passed)spin test -- -q -k "not docstrings"(456 passed)cython-lint src/The full doctest collection was also attempted under a local CPython 3.14 free-threaded build; it has pre-existing doctest namespace failures unrelated to this change, so the passing general and focused suites above are the relevant evidence.