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/3434#issuecomment-549407230,https://api.github.com/repos/pydata/xarray/issues/3434,549407230,MDEyOklzc3VlQ29tbWVudDU0OTQwNzIzMA==,1191149,2019-11-04T15:30:08Z,2019-11-04T15:30:08Z,CONTRIBUTOR,Got it. This is a test update to a test that is backward and forward compatible. I'll get something checked in.,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,510915725
https://github.com/pydata/xarray/issues/3434#issuecomment-548458836,https://api.github.com/repos/pydata/xarray/issues/3434,548458836,MDEyOklzc3VlQ29tbWVudDU0ODQ1ODgzNg==,1191149,2019-10-31T16:29:32Z,2019-10-31T16:29:32Z,CONTRIBUTOR,"I believe there are two issues here.

First, the 3.1 release was not 2.7 compliant. It mixed named keyword arguments with `**kwds`. That could be fixed easily.

Second, the camx reader changed subclasses, which affects the xarray test for CF variables. I could update the test that would fix xarray test-case.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,510915725