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/3349#issuecomment-537622127,https://api.github.com/repos/pydata/xarray/issues/3349,537622127,MDEyOklzc3VlQ29tbWVudDUzNzYyMjEyNw==,1217238,2019-10-02T18:30:25Z,2019-10-02T18:30:25Z,MEMBER,"It seems like these are getting reinvented often enough that it's worth
pulling some of these into xarray proper.
On Wed, Oct 2, 2019 at 9:04 AM Ryan Abernathey
wrote:
> I'm getting deja-vu here... Xscale has a huge and impressive sounding API.
> But no code coverage and no commits since January. Like many of these
> projects, it seems to have bit off more than its maintainers could chew.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> ,
> or mute the thread
>
> .
>
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,499477363
https://github.com/pydata/xarray/issues/3349#issuecomment-536690748,https://api.github.com/repos/pydata/xarray/issues/3349,536690748,MDEyOklzc3VlQ29tbWVudDUzNjY5MDc0OA==,1217238,2019-09-30T18:29:10Z,2019-09-30T18:29:10Z,MEMBER,"From a user perspective, I think people prefer to find stuff in one place.
From a maintainer perspective, as long as it's somewhat domain agnostic (e.g., ""physical sciences"" rather than ""oceanography"") and written to a reasonable level of code quality, I think it's fine to toss it into xarray. ""Already exists in NumPy/SciPy"" is probably a reasonable proxy for the former.
So I say: yes, let's toss in polyfit, along with fast fourier transforms.
If we're concerned about clutter, we can put stuff in a dedicated namespace, e.g., `xarray.wrappers`.","{""total_count"": 3, ""+1"": 3, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,499477363