issues: 530777706
This data as json
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
530777706 | MDU6SXNzdWU1MzA3Nzc3MDY= | 3586 | Update documentation to reflect removal of inplace option | 1328158 | closed | 0 | 1 | 2019-12-01T18:58:53Z | 2020-12-12T23:10:11Z | 2020-12-12T23:10:11Z | NONE | MCVE Code Sample```python Your code hereds_gamma.reset_coords('month', drop=True, inplace=True) ~/miniconda3/envs/spi_multi/lib/python3.8/site-packages/xarray/core/utils.py in _check_inplace(inplace)
38 def _check_inplace(inplace: Optional[bool]) -> None:
39 if inplace is not None:
---> 40 raise TypeError(
41 "The TypeError: The Expected OutputCoordinates reset in-place, or documentation that does not list Problem DescriptionThe documentation for This appears to have been addressed before in issue #858 but maybe the inplace argument slipped back into the documentation somehow? I see that there is a function to check for an inplace argument and raise an error if present -- why is this being used rather than removing the inplace argument altogether? Is this mechanism in place to facilitate backward compatibility, etc.? Output of
|
{ "url": "https://api.github.com/repos/pydata/xarray/issues/3586/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | 13221727 | issue |