Merged
Conversation
ianna
commented
Aug 8, 2025
Member
Author
ianna
left a comment
There was a problem hiding this comment.
The deprecation warning for the JAX backend is clear and appropriately placed to alert users ahead of removal. The message is visible during tests and runtime, ensuring good visibility.
This aligns well with the ongoing discussion and planned removal after the JAX branching.
I approve merging this PR for inclusion in the next release.
DeprecationWarning
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.
Description:
This PR adds a
DeprecationWarningto the Jax nplike backend, notifying users that JAX support in Awkward Array will be deprecated and removed in a future release.Changes:
Rationale:
The JAX backend in Awkward Array is no longer actively maintained and is planned for removal in an upcoming release. Adding an explicit deprecation warning will ensure that downstream users are aware of this change before it happens, giving them time to adapt their code.
Note:
ak.to_jaxandak.from_jaxwill continue to be maintained for interoperability with JAX, even after the backend is removed.Example Warning Output:
Next Steps:
If there are any comments or suggestions, please add them to the ongoing discussion: #3603