pull_requests: 1565418769
This data as json
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1565418769 | PR_kwDOAMm_X85dTmUR | 8341 | closed | 0 | Deprecate tuples of chunks? | 5635139 | (I was planning on putting an issue in, but then thought it wasn't much more difficult to make the PR. But it's totally fine if we don't think this is a good idea...) Allowing a tuple of dims means we're reliant on dimension order, which we really try and not be reliant on. It also makes the type signature even more complicated. So are we OK to encourage a dict of `dim: chunksize`, rather than a tuple of chunksizes? | 2023-10-19T18:44:25Z | 2023-10-21T01:45:28Z | 2023-10-21T00:49:19Z | 2023-10-21T00:49:19Z | 126b92af2de63d1fb9aca2cc3879f2e2908877b8 | 0 | 63be4f7091d3535c5b5e3ab9c5a7d7f025bd1da1 | 8dddbca924fac1012245f510dca282f7f125cb06 | MEMBER | 13221727 | https://github.com/pydata/xarray/pull/8341 |
Links from other tables
- 2 rows from pull_requests_id in labels_pull_requests