issues

Table actions

3 rows where comments = 17 and user = 2448579 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date), closed_at (date)

state 2

type 1

repo 1

id node_id number title user state locked assignee milestone comments created_at updated_at ▲ closed_at author_association active_lock_reason draft pull_request body reactions performed_via_github_app state_reason repo type
1950211465 I_kwDOAMm_X850Pd2J 8333 Should NamedArray be interchangeable with other array types? or Should we support the `axis` kwarg? dcherian 2448579 open 0     17 2023-10-18T16:46:37Z 2023-10-31T22:26:33Z   MEMBER      

What is your issue?

Raising @Illviljan's comment from https://github.com/pydata/xarray/pull/8304#discussion_r1363196597.

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/8333/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 issue
476222321 MDU6SXNzdWU0NzYyMjIzMjE= 3178 type annotations make docs confusing dcherian 2448579 closed 0     17 2019-08-02T14:57:33Z 2020-05-19T16:49:26Z 2020-05-19T16:49:26Z MEMBER      

The annotations make this signature basically unreadable to anyone not familiar with them.

Is there a way to hide them in the documentation? Or at least change formatting so it's clearer what the function arguments are?

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/3178/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed xarray 13221727 issue
551484736 MDU6SXNzdWU1NTE0ODQ3MzY= 3702 release 0.15.0? dcherian 2448579 closed 0     17 2020-01-17T15:38:30Z 2020-02-03T17:04:40Z 2020-02-03T17:04:40Z MEMBER      

It's been 2 months since our last release. It'd be nice to issue one soon; mostly to get the really nice documentation changes out.

According to our min versions policy we can bump up to numpy 1.15 and dask 2.2 (though we need to solve #3660 first). So I propose we do that and bump to 0.15.0

must-have:

  • [x] #3660
  • [x] #3713
  • [x] #3560
  • [x] #3673 - waiting on upstream fix.

close/ready and nice to have:

  • [ ] #3691
  • [ ] #3588
  • [x] #3670
  • [x] #3631
  • [ ] #3611
  • [ ] #3610
  • [x] #3618
 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/3702/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed xarray 13221727 issue

Advanced export

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

CSV options: 

CREATE TABLE [issues] (
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [number] INTEGER,
   [title] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [state] TEXT,
   [locked] INTEGER,
   [assignee] INTEGER REFERENCES [users]([id]),
   [milestone] INTEGER REFERENCES [milestones]([id]),
   [comments] INTEGER,
   [created_at] TEXT,
   [updated_at] TEXT,
   [closed_at] TEXT,
   [author_association] TEXT,
   [active_lock_reason] TEXT,
   [draft] INTEGER,
   [pull_request] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [state_reason] TEXT,
   [repo] INTEGER REFERENCES [repos]([id]),
   [type] TEXT
);
CREATE INDEX [idx_issues_repo]
    ON [issues] ([repo]);
CREATE INDEX [idx_issues_milestone]
    ON [issues] ([milestone]);
CREATE INDEX [idx_issues_assignee]
    ON [issues] ([assignee]);
CREATE INDEX [idx_issues_user]
    ON [issues] ([user]);