Skip to content

BUG: Do not accidentally store dtype metadata in np.save #27143

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 8, 2024

Conversation

seberg
Copy link
Member

@seberg seberg commented Aug 8, 2024

We had logic in place to drop (most) metadata, but the change had a small bug: During saving, we were still using the one with metadata...

Maybe doesn't quite close it, but big enough of an improvement for now, I think, so

Closes gh-14142

@seberg seberg added the 00 - Bug label Aug 8, 2024
We had logic in place to drop (most) metadata, but the change
had a small bug: During saving, we were still using the one with
metadata...

Maybe doesn't quite close it, but big enough of an improvement
for now, I think, so

Closes numpygh-14142
@charris charris added the 09 - Backport-Candidate PRs tagged should be backported label Aug 8, 2024
@charris
Copy link
Member

charris commented Aug 8, 2024

Is a backport also needed to 2.0?

@seberg
Copy link
Member Author

seberg commented Aug 8, 2024

This has been around for a long time, so don't care, but maybe Tom does. Since the metadata dropping worked and I think loading never really did, I think it is save to backport to 2.0, though/

@charris charris merged commit 7e5dc82 into numpy:main Aug 8, 2024
66 checks passed
@charris
Copy link
Member

charris commented Aug 8, 2024

Thanks Sebastian.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Failure to load .npy file with structured dtype and metadata
2 participants