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/1876#issuecomment-365746775,https://api.github.com/repos/pydata/xarray/issues/1876,365746775,MDEyOklzc3VlQ29tbWVudDM2NTc0Njc3NQ==,2443309,2018-02-14T21:13:13Z,2018-02-14T21:13:13Z,MEMBER,"A practical change we need to make prior to dropping python 2 is to move the Python 2 test suite to Python 3. A number of Xarray's optional dependencies are still pinned to Python 2 so there will be a few hiccups there:

- PyNIO: A Python 3 compatible release is forthcoming, see https://github.com/NCAR/pynio/issues/17.
- CDAT: I'm not sure if there is Python 3 support yet. The conda-forge build only has Py2. 

Ideally, we can just map the py2 tests directly to py3:

- `py27-min` --> `py35-min`
- `py27-cdat+iris+pynio` --> py36-cdat+iris+pynio

We may also consider dropping this test all together and putting cdat/iris/pynio in the standard `py36` test.","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,293414745
https://github.com/pydata/xarray/issues/1876#issuecomment-362185062,https://api.github.com/repos/pydata/xarray/issues/1876,362185062,MDEyOklzc3VlQ29tbWVudDM2MjE4NTA2Mg==,10050469,2018-02-01T07:48:39Z,2018-02-01T07:48:39Z,MEMBER,"Thanks! The [practicalities](http://www.python3statement.org/practicalities/) page from the python3statement is a good start.

What I heard from other projects is that we shouldn't *actively* remove cross-compatible code. We could simply stop testing on py2 and not care about cross-compatibility anymore. ","{""total_count"": 2, ""+1"": 2, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,293414745