FIX: the new _AxesStack with np.array as input #9029
Closed
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
This adds a layer checking in the case where a numpy array is passed as a value (either in args or kwargs).
|
The other option is to revert my merge of #7377 |
|
I would suggest just checking for pickle equality (in fact, one could just store the pickles of the keys instead of the keys themselves), which seems a lot simpler than adding another 30 lines to support a soon-to-be-deprecated behavior. |
|
Closing in favor of:
|
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.
PR Summary
This adds a layer checking in the case where a numpy array is
passed as a value (either in args or kwargs).
fixes a bug that was in #7377 that I missed when I merged it.
PR Checklist