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

Retain label type in .to_dataset #749

Merged
merged 1 commit into from
Feb 14, 2016
Merged

Retain label type in .to_dataset #749

merged 1 commit into from
Feb 14, 2016

Conversation

max-sixty
Copy link
Collaborator

Not sure if this was a deliberate choice (maybe so integer indexing wasn't disrupted?). This allows objects as dataset keys / labels.

Let me know your thoughts and I'll add a what's new.

(I know I have a few PRs dangling - apologies - will go back and clean them up soon)

@max-sixty max-sixty changed the title Retain labels to .to_dataset, even if not strings Retain label type in .to_dataset, even if not strings Feb 8, 2016
@max-sixty max-sixty changed the title Retain label type in .to_dataset, even if not strings Retain label type in .to_dataset Feb 8, 2016
@jhamman
Copy link
Member

jhamman commented Feb 8, 2016

@shoyer - I don't remember which issue it was but I seem to remember implementing this on purpose. I think we were having trouble serializing and round-tripping with non string type labels. Ring a bell?

@shoyer
Copy link
Member

shoyer commented Feb 8, 2016

I recall discussing this and coming to the conclusion that any hashable object should be valid as dataset keys. Obviously, you need strings if you want to use standard serialization backends, but otherwise it's better to keep things flexible.

@shoyer
Copy link
Member

shoyer commented Feb 13, 2016

@MaximilianR could please add a quick what's new note? otherwise this looks good to me

@max-sixty
Copy link
Collaborator Author

@shoyer Added What's New - cheers

shoyer added a commit that referenced this pull request Feb 14, 2016
@shoyer shoyer merged commit d516209 into pydata:master Feb 14, 2016
@max-sixty max-sixty deleted the no-coerce-dateset-keys-to-str branch February 16, 2016 03:51
flamingbear added a commit to flamingbear/xarray that referenced this pull request Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants