issues: 58025732

This data as json

id node_id number title user state locked assignee milestone comments created_at updated_at closed_at author_association active_lock_reason draft pull_request body reactions performed_via_github_app state_reason repo type
58025732 MDU6SXNzdWU1ODAyNTczMg== 323 Datetime parsing errors should be raised when opening datasets, not when values are accessed 1217238 closed 0     0 2015-02-18T04:44:39Z 2015-02-23T03:11:03Z 2015-02-23T03:11:03Z MEMBER      

As discussed in #316:

@sjpfenninger:

However, I'm still not quite happy with the way errors were/are handled: before this change, reading a file with the non-standard datetime format would work without errors, but trying to do anything with the dataset after opening it would produce a ValueError, which from an end-user perspective doesn't help much to figure out where the error is coming from.

@shoyer:

I agree, this is not ideal. We really should try to decode time units at the time a dataset is opened, not just when the values are read (which open leads to a failed repr()). Adding some sort of more helpful error message to catch exception that arise would also help (e.g., "cannot read non-ISO time units: netCDF4 not installed").

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/323/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed 13221727 issue

Links from other tables