Conversation
Each tuple was built from a set of strings, so its order changed with Python's hash seed and printing a collection gave different output from run to run. The common types now keep the order of the first member.
Member
Author
|
This one is a pain for doctests. |
This branch has not been deployed
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
1 participant
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 Description
NDCollection.aligned_axis_physical_types built each tuple from a set, so the order of the physical types changed with Python's hash seed. Printing a collection, or anything else that shows these types (such as downstream docs), gave different output from run to run.
AI Assistance Disclosure
AI tools were used for:
K.