home / github

Menu
  • GraphQL API
  • Search all tables

pull_requests

Table actions
  • GraphQL API for pull_requests

2 rows where user = 14276158

✎ View and edit SQL

This data as json, CSV (advanced)

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

id ▼ node_id number state locked title user body created_at updated_at closed_at merged_at merge_commit_sha assignee milestone draft head base author_association auto_merge repo url merged_by
838161344 PR_kwDOAMm_X84x9VPA 6232 closed 0 Amended docstring to reflect the actual behaviour of Dataset.map lpilz 14276158 In [MetPy/pull#2312](https://github.com/MetPy/pull/2312), I noticed that the behavior of `Dataset.map`'s kwarg `keep_attrs` was not in line with its docstring. This is because in xarray 0.16.2 (pydata/xarray#3595 & pydata/xarray#4195) this behavior was changed. In short, `keep_attrs=True` now copies both, the Dataset's and the variables' attributes and adds them to the new objects - preventing any change to them by the mapped function. In contrast, `keep_attrs= False` discards the Dataset's attributes and does not touch the variables' attributes, enabling the mapped function to modify them. Here, I propose an update to the `keep_attrs` docstring of `Dataset.map` which would more accurately reflect its current behavior. Please feel free to provide alternative formulations if you feel like this one misses the mark. 2022-02-02T10:39:30Z 2022-02-23T09:51:41Z 2022-02-23T09:51:27Z 2022-02-23T09:51:27Z b760807646cce493cf8f4f619fcda9a14e84670f     0 0dacffa52cd3f32d8871c87369f5269743f46e0b 86328a1cfe5296f8e478b17e52ba884db2384872 CONTRIBUTOR   xarray 13221727 https://github.com/pydata/xarray/pull/6232  
861240194 PR_kwDOAMm_X84zVXuC 6292 closed 0 Amended docs on how to add a new backend lpilz 14276158 When trying to install a new xarray backend with poetry, I noticed that it should be `xarray.backends` instead of `xarray_backends`. 2022-02-23T10:11:06Z 2022-02-23T17:54:53Z 2022-02-23T17:54:47Z 2022-02-23T17:54:47Z de965f342e1c9c5de92ab135fbc4062e21e72453     0 1fff7fa661987553a67ccfe54ba419ef74220af6 b760807646cce493cf8f4f619fcda9a14e84670f CONTRIBUTOR   xarray 13221727 https://github.com/pydata/xarray/pull/6292  

Advanced export

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

CSV options:

CREATE TABLE [pull_requests] (
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [number] INTEGER,
   [state] TEXT,
   [locked] INTEGER,
   [title] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [body] TEXT,
   [created_at] TEXT,
   [updated_at] TEXT,
   [closed_at] TEXT,
   [merged_at] TEXT,
   [merge_commit_sha] TEXT,
   [assignee] INTEGER REFERENCES [users]([id]),
   [milestone] INTEGER REFERENCES [milestones]([id]),
   [draft] INTEGER,
   [head] TEXT,
   [base] TEXT,
   [author_association] TEXT,
   [auto_merge] TEXT,
   [repo] INTEGER REFERENCES [repos]([id]),
   [url] TEXT,
   [merged_by] INTEGER REFERENCES [users]([id])
);
CREATE INDEX [idx_pull_requests_merged_by]
    ON [pull_requests] ([merged_by]);
CREATE INDEX [idx_pull_requests_repo]
    ON [pull_requests] ([repo]);
CREATE INDEX [idx_pull_requests_milestone]
    ON [pull_requests] ([milestone]);
CREATE INDEX [idx_pull_requests_assignee]
    ON [pull_requests] ([assignee]);
CREATE INDEX [idx_pull_requests_user]
    ON [pull_requests] ([user]);
Powered by Datasette · Queries took 20.267ms · About: xarray-datasette