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/pull/59#issuecomment-37503963,https://api.github.com/repos/pydata/xarray/issues/59,37503963,MDEyOklzc3VlQ29tbWVudDM3NTAzOTYz,514053,2014-03-13T06:32:59Z,2014-03-13T06:32:59Z,CONTRIBUTOR,"Yeah, does seem that way.  Unfortunately that makes comparison with datetime objects a bit awkward.  Perhaps we should include a to_datetime() the way pandas does?  Certainly, it would be convenient to be able to do comparisons such as:

ds['time'].data > datetime.datetime(2014, 01, 01)

This is definitely not high priority though. 
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,29067976
https://github.com/pydata/xarray/pull/59#issuecomment-37433623,https://api.github.com/repos/pydata/xarray/issues/59,37433623,MDEyOklzc3VlQ29tbWVudDM3NDMzNjIz,514053,2014-03-12T16:55:52Z,2014-03-12T16:55:52Z,CONTRIBUTOR,"I'll go ahead and merge this in to fix the bug ... but I wonder if there is any way we can avoid using np.datetime64 objects.  They seem under-developed / broken.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,29067976