Fix dtype comparison using 'is' instead of '==' in _integrate.py #679
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
- Replace 'is' with '==' for dtype comparisons on lines 265 and 388 - Fixes assertion errors in scenarios involving serialization/distributed computing - Ensures robust dtype comparison regardless of how dtype objects are created - Maintains backward compatibility and intended behavior Fixes patrick-kidger#678
Owner
|
Awesome, thank you for the clear issue description and for fix! This LGTM, so merged :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 Bug Report: Incorrect dtype comparison using
isinstead of==in _integrate.py #678