BUG: Make sure numpy globals keep identity after reload. #7941
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.
Given that pandas, matplotlib, and astropy all reload numpy, the preferred solution of raising and error when a reload is attempted is too draconian. This PR takes the approach of making numpy reload safer by moving the needed globals into their own
_globals.py
module from which they can be imported when numpy reloads. Unless_globals.py
itself is reloaded, not just imported from, the identity of the globals will remain intact.