issue_comments

Table actions

3 rows where author_association = "MEMBER", issue = 602256880 and user = 2443309 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date)

user 1

  • jhamman · 3 ✖

issue 1

  • [Proposal] Expose Variable without Pandas dependency · 3 ✖

author_association 1

  • MEMBER · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
985824018 https://github.com/pydata/xarray/issues/3981#issuecomment-985824018 https://api.github.com/repos/pydata/xarray/issues/3981 IC_kwDOAMm_X846wnsS jhamman 2443309 2021-12-03T20:59:27Z 2021-12-03T20:59:27Z MEMBER

@andy-sweet - please do join the next call. I've added it to the meeting agenda. 

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   [Proposal] Expose Variable without Pandas dependency 602256880
985051449 https://github.com/pydata/xarray/issues/3981#issuecomment-985051449 https://api.github.com/repos/pydata/xarray/issues/3981 IC_kwDOAMm_X846trE5 jhamman 2443309 2021-12-02T22:25:29Z 2021-12-02T22:25:39Z MEMBER

Hi @sofroniewn - This is certainly something we still want to work on (see this section of our current roadmap and a more detailed proposal that included work in this area). I actually think the relevant part of the linked proposal is the best we have for a working plan here (text copied from doc below):

Xvariable: New lightweight Variable API (labeled arrays without coordinates)

This work area is about cleaning up Xarray’s internals, and allowing our low-level “Variable” data structure to be usable by other projects in the scientific Python ecosystem. We have identified the following key tasks and deliverables:

a. Formalize Xarray’s contract for valid data inside “Variable”, and remove/replace some legacy features that would be hard to justify for a generic library: 1. Move the “encoding” attribute from “Variable” onto a new “duck array” class that can be used inside a “Variable” (#5082) 2. Expose Xarray’s internal model for “explicit array indexing” as a public API. Xarray uses this feature because supporting the full complexity of NumPy’s full indexing API is hard for many array implementations.

b. Separate out and possibly rename/re-brand to Xvariable parts of Xarray internals into new projects. This will increase their visibility, find new users for these tools and improve the maintainability of Xarray itself. 1. The ”Variable” class will move into a separate project that only depends upon NumPy, and that Xarray in-turn will depend upon. We hope this project will be of interest to users interested in simpler tools than Xarray (#3981). 2. The new package will support indexing and a limited series of other operations lazily on arrays loaded from disk or remote storage, without loading the entire array into memory. This project is of interest to other projects such as Napari (#5081).

c. API stabilization, code consolidation and maintenance of the external project.

We have a bi-weekly developer call on Wednesday mornings (#4001), one idea would be devote 10-15 minutes of our next meeting to this topic. Is that something you and/or @andy-sweet would be up for joining?

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   [Proposal] Expose Variable without Pandas dependency 602256880
615494816 https://github.com/pydata/xarray/issues/3981#issuecomment-615494816 https://api.github.com/repos/pydata/xarray/issues/3981 MDEyOklzc3VlQ29tbWVudDYxNTQ5NDgxNg== jhamman 2443309 2020-04-17T22:40:59Z 2020-04-17T22:40:59Z MEMBER

Thanks @amueller! You're not the only group that has voiced interest in an index-free labeled array so I think its still worth discussing.

I think right now we're most concerned about sparse data representations (and I was considering asking you folks if you'd support scipy.sparse ;

We have recently added support for pydata/sparse. We need to document this better (#3484). This work is not 100% complete (https://github.com/pydata/xarray/issues/3213) and is part of Xarray's larger goal of supporting duck arrays. Please chime in on one of those issues so we can go a bit deeper.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   [Proposal] Expose Variable without Pandas dependency 602256880

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);