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/1332#issuecomment-289840161,https://api.github.com/repos/pydata/xarray/issues/1332,289840161,MDEyOklzc3VlQ29tbWVudDI4OTg0MDE2MQ==,4295853,2017-03-28T17:14:29Z,2017-03-28T17:14:29Z,CONTRIBUTOR,"@rabernat, do you think that the proposed keyword additions should be included in xarray or not?  I personally would like to see them in xarray but don't know if it is just me or not.  If you think they should be in xarray, are you ok with the api above?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,217385961
https://github.com/pydata/xarray/issues/1332#issuecomment-289833779,https://api.github.com/repos/pydata/xarray/issues/1332,289833779,MDEyOklzc3VlQ29tbWVudDI4OTgzMzc3OQ==,4295853,2017-03-28T16:52:25Z,2017-03-28T16:52:25Z,CONTRIBUTOR,"@shoyer, I'm not sure we want to wrap `np.gradient`.  It seems like other approaches like @rabernat 's `xgcm` would be more appropriate as a superset of xarray.  

Fundamentally, I want something that is like an inverse of `cumsum` and the proposed change could be used in that context.  It is just super inconvenient to do array resizing following the diff of a time vector to get timesteps, but maybe this use case is too niche to be useful for the community.","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,217385961