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/1850#issuecomment-483336107,https://api.github.com/repos/pydata/xarray/issues/1850,483336107,MDEyOklzc3VlQ29tbWVudDQ4MzMzNjEwNw==,1217238,2019-04-15T17:03:27Z,2019-04-15T17:03:27Z,MEMBER,"@teoliphant thanks for sharing your thoughts! I would be very happy to collaborate on what a protocol for labeled arrays in Python could look like. Xarray is one useful implementations of labeled arrays, but it's definitely not the only one.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,290593053 https://github.com/pydata/xarray/issues/1850#issuecomment-483333879,https://api.github.com/repos/pydata/xarray/issues/1850,483333879,MDEyOklzc3VlQ29tbWVudDQ4MzMzMzg3OQ==,1217238,2019-04-15T16:57:08Z,2019-04-15T16:57:08Z,MEMBER,"For what it's worth, TensorFlow has decided that bundling contrib modules into TensorFlow as `tensorflow.contrib` was a big mistake. It helped with discoverability, but resulted in a lot of confusion about what is a supported API and what isn't.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,290593053 https://github.com/pydata/xarray/issues/1850#issuecomment-368201831,https://api.github.com/repos/pydata/xarray/issues/1850,368201831,MDEyOklzc3VlQ29tbWVudDM2ODIwMTgzMQ==,1217238,2018-02-24T05:30:01Z,2018-02-24T05:30:01Z,MEMBER,"Personally I'd rather have ""awesome xarray"" listed somewhere prominently in the xarray docs, along with mentions inline in the docs anywhere where they are particularly relevant . The very short list that is currently there is based upon a handful of projects that I knew about a few years ago, but it's definitely woefully out of date now. On Fri, Feb 23, 2018 at 9:23 PM Noah D Brenowitz wrote: > @maxim-lian There is a very short list of > such packages hidden in the xarray documention > > . > > In general, there are a ton of these awesome-... repos floating around > the internet which just list the useful/related tools/libraries which are > related to ... . For example, there are repos out there like > awesome-python and awesome-bash. > Maybe someone could start an awesome-xarray package. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > , or mute > the thread > > . > ","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,290593053 https://github.com/pydata/xarray/issues/1850#issuecomment-359959683,https://api.github.com/repos/pydata/xarray/issues/1850,359959683,MDEyOklzc3VlQ29tbWVudDM1OTk1OTY4Mw==,1217238,2018-01-23T22:54:51Z,2018-01-23T22:54:51Z,MEMBER,"I think domain specific dependencies are a pretty decisive argument in favor of the separate repository model. TensorFlow doesn't relax its code quality standards for contrib packages -- it's more about reducing guarantees of API stability or maintenance. That works OK for TensorFlow in part because the authors of most contrib packages are Google software engineers.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,290593053