pull_requests: 310584059
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 310584059 | MDExOlB1bGxSZXF1ZXN0MzEwNTg0MDU5 | 3260 | closed | 0 | Raise on inplace=True | 5635139 | <!-- Feel free to remove check-list items aren't relevant to your change --> - [x] Removes inplace, and relatedly closes https://github.com/pydata/xarray/issues/1997 (and maybe https://github.com/pydata/xarray/issues/2951) - [x] Passes `black . && mypy . && flake8` - [x] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API - [x] Remove from doc strings, docs Do we want to raise an explicit error for another minor release (rather than remove all traces of `inplace`)? I'd vote +0.5 - it's likely that some people don't check deprecation warnings and this states the problem clearly What do we want to do re `.update` (#2951)? | 2019-08-24T04:55:08Z | 2019-08-26T18:44:00Z | 2019-08-26T18:43:51Z | 2019-08-26T18:43:51Z | e3b3bed2c2e27eb74adc2b7f80c365c2928cd78b | 0 | 277fdd95e90e046b57595cd9639a02faac8ad049 | 5f55d41a05618e6091061dfb83fe745ed6008997 | MEMBER | 13221727 | https://github.com/pydata/xarray/pull/3260 |
Links from other tables
- 0 rows from pull_requests_id in labels_pull_requests