issue_comments: 685200043

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/4183#issuecomment-685200043 https://api.github.com/repos/pydata/xarray/issues/4183 685200043 MDEyOklzc3VlQ29tbWVudDY4NTIwMDA0Mw== 90008 2020-09-02T00:13:30Z 2020-09-02T00:13:30Z CONTRIBUTOR

i ran into this problem trying to round trip time to the nanosecond (even though i don't need it, sub micro second would be nice)

but unfrotunately, you run into the fact that cftime doesn't support nanoseconds https://github.com/Unidata/cftime/blob/master/cftime/_cftime.pyx

Seems like they discussed a nanosecond issue a while back too https://github.com/Unidata/cftime/issues/77

Their ultimate point was that there was little point in having precision down to the nano second given that python datetime objects only have microseconds. I guess they are right.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   646038170