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/1353#issuecomment-292260729,https://api.github.com/repos/pydata/xarray/issues/1353,292260729,MDEyOklzc3VlQ29tbWVudDI5MjI2MDcyOQ==,1050278,2017-04-06T18:12:18Z,2017-04-06T18:12:18Z,CONTRIBUTOR,"@shoyer Agreed, there is no need for `xarray.tests` to be importable.  Closing this issue, thanks for the quick clarification.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,219611498
https://github.com/pydata/xarray/issues/1353#issuecomment-292237368,https://api.github.com/repos/pydata/xarray/issues/1353,292237368,MDEyOklzc3VlQ29tbWVudDI5MjIzNzM2OA==,1217238,2017-04-06T16:57:00Z,2017-04-06T16:57:00Z,MEMBER,@jjhelmus see conda-forge/xarray-feedstock#20,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,219611498
https://github.com/pydata/xarray/issues/1353#issuecomment-292236298,https://api.github.com/repos/pydata/xarray/issues/1353,292236298,MDEyOklzc3VlQ29tbWVudDI5MjIzNjI5OA==,1217238,2017-04-06T16:53:11Z,2017-04-06T16:53:11Z,MEMBER,"@jjhelmus Agreed! For testing public API, being able to import `xarray` and `xarray.backends` should be enough.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,219611498
https://github.com/pydata/xarray/issues/1353#issuecomment-292195182,https://api.github.com/repos/pydata/xarray/issues/1353,292195182,MDEyOklzc3VlQ29tbWVudDI5MjE5NTE4Mg==,1050278,2017-04-06T14:38:57Z,2017-04-06T14:38:57Z,CONTRIBUTOR,"> Just out of curiosity, what reason did you have for importing xarray.tests?

`xarray.tests` is listed as a import test in the [conda-forge xarray-feedstock](https://github.com/conda-forge/xarray-feedstock) and was failing when I was doing a build.  I do not think that import line needs to be present, `tests` does not seem to be in the public API of xarray.  I'd be in favor of removing that line and keeping the test suite setup as-is.","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,219611498
https://github.com/pydata/xarray/issues/1353#issuecomment-292089134,https://api.github.com/repos/pydata/xarray/issues/1353,292089134,MDEyOklzc3VlQ29tbWVudDI5MjA4OTEzNA==,1217238,2017-04-06T07:13:59Z,2017-04-06T07:13:59Z,MEMBER,"Hmm. This seems like an easy way to add a few options to running our test suite, but maybe there is a better way to do this? I guess we could hack in a fallback with `hasattr()` but that's pretty ugly.

Just out of curiosity, what reason did you have for importing `xarray.tests`?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,219611498
https://github.com/pydata/xarray/issues/1353#issuecomment-291901003,https://api.github.com/repos/pydata/xarray/issues/1353,291901003,MDEyOklzc3VlQ29tbWVudDI5MTkwMTAwMw==,1050278,2017-04-05T15:36:00Z,2017-04-05T15:36:00Z,CONTRIBUTOR,"pytest-dev/pytest#472 from [BitBucket #472](https://bitbucket.org/pytest-dev/pytest/issues/472) seems to touch on this topic and references the note found at the end of the [skip and xfail documentation](https://docs.pytest.org/en/latest/skipping.html):

> You cannot use pytest.config.getvalue() in code imported before pytest’s argument parsing takes place. 
> For example, conftest.py files are imported before command line parsing and thus config.getvalue() will not execute correctly.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,219611498