issue_comments: 42258925
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/53#issuecomment-42258925 | https://api.github.com/repos/pydata/xarray/issues/53 | 42258925 | MDEyOklzc3VlQ29tbWVudDQyMjU4OTI1 | 327925 | 2014-05-06T01:17:16Z | 2014-05-06T01:17:16Z | MEMBER | Outstanding issue: What to do with unicode data (the native str type on Python 3 is unicode). The SciPy netcdf module doesn't attempt to handle unicode, so I wrote some code to encode unicode to bytes before storing it in scipy. That means, however, that the roundtrip doesn't work, because loading the data again gives bytes, not str. The netCDF4 module appears to handle this by just decoding any string data it finds to unicode, without considering what it's intended to be. Options: - Decode all string data to unicode on load. This is consistent with what netCDF already does. - Store the fact that the data was encoded in an attribute in the file. If that attribute is present, decode it again on load. - Don't decode any data, and change all the scipy roundtrip tests to expect that data comes back as bytes. I'm not familiar enough with netCDF and how it's used to know what makes sense here. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
28940534 |