Replies: 1 comment 2 replies
-
The warning arises because To be clear, your new code is functionally identical to the old code in current JAX releases, but will not be functionally identical in future releases, because the semantics of your original code will change (thus the deprecation warning). Does that make sense? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello everyone :)
The following code snippets rises a
DeprecationWarning
in the last version of JAX which, to my understanding, shouldn't be there. The code isBasically, I filter
tree
by selecting only the subtrees with selectedNode
s as a root, based onfilter
. Here, the idea is thatfilter
has been modified by replacing all the excludedNode
s with None.In particular the warning I get is
which makes me wonder if the code I wrote is behaving as expected, since it relies on the fact the None values are excluded from consideration, while the message seems to indicate that now they are included (and will only be excluded in future versions)?
To remove the warning I can write:
which to me should be functionally identical to the original code.
Am I missing something?
Beta Was this translation helpful? Give feedback.
All reactions