Skip to content
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

API inconsistency: set_dataset(..., save=True) vs get_dataset(..., archive=True) #1171

Closed
jordens opened this issue Oct 9, 2018 · 2 comments

Comments

@jordens
Copy link
Member

jordens commented Oct 9, 2018

It would be clearer and leave fewer chances for errors to call them both archive since the functionality is the same. Or am I missing something?

@sbourdeauducq
Copy link
Member

Agreed. If no one objects, I'll add archive to set_dataset while keeping save (for backward compatibility and with a warning; we can e.g. do that in 4.0 and remove it completely in 5.0).

@jordens
Copy link
Member Author

jordens commented Oct 22, 2018

The slightly confusing wrinkle (and probably the reason it was not like this before) is the following behavior:
Something that has been set with set(..., archive=True) does not appear in the archive group (but in the datasets group) in the HDF5 but something from get(..., archive=True) does appear in the archive group.
Since we treat the datasets (and the "archive" stuff) as a single namespace anyway we might also merge the two groups.

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

No branches or pull requests

2 participants