issue_comments: 391470885
This data as json
html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
https://github.com/pydata/xarray/issues/2176#issuecomment-391470885 | https://api.github.com/repos/pydata/xarray/issues/2176 | 391470885 | MDEyOklzc3VlQ29tbWVudDM5MTQ3MDg4NQ== | 11411331 | 2018-05-23T19:37:26Z | 2018-05-23T19:37:26Z | CONTRIBUTOR | Thanks, @jhamman, for the reference. I have, indeed, been thinking about this a lot. I've hit the same problem that you have @mcgibbon and came to the same conclusion that subclassing was the only way to go. I'm not sure I'm happy with my solution, but I wrote a (partial) implementation of a DataArray subclass to deal with units. @jhamman suggested that I pull this out into a separate repo, and I hope to do that one day... However, if you are curious, now, you can view it here: https://github.com/NCAR/PyConform/tree/rewrite/source/pyconform/physarrays Note that this implementation deals with time as just another unit, rather than requiring any special dealing with time. This works if you units package can deal with calendared times, too. I am currently using Also, note that this implementation also deals with the Let me know what you think about this. If it's a priority, I can pull this out into its own repository. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
325810810 |