pull_requests: 815158265
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 815158265 | PR_kwDOAMm_X84wllP5 | 6144 | closed | 0 | allow 1 non-null value in interpolate_na with method="nearest" | 3698640 | - [x] Closes #5994 - [x] Tests added - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` @Skealz's great issue (#5994) highlighted that DataArrays with a single non-null value raise an error if `DataArray.interpolate_na` is called with `method='nearest'`. Note that this does not occur for the default (`method='linear'`). In this PR: * Uses the "fast track" to quickly return *any* 1-D slices with a single non-null value in addition to the previous all-nan or no-nan fasttrack * Explicitly check this behavior for all 1-D interpolation methods using parametrized tests * consolidate other fast-track tests (`interpolate_allnans` and `interpolate_nonans`) into a single parameterized test For discussion: * This patch may break existing workflows if they rely on the current behavior, which errors for slices with only a single value | 2022-01-06T01:28:17Z | 2022-01-19T03:33:19Z | 2022-01-18T22:45:39Z | 2022-01-18T22:45:39Z | 8c0166cba410eb96c18efbc34d7d8af8e448df6e | 0 | 5a8736b8e0d7f06e839c3c09ef7fe9c5aadebd8c | 3666a6fb7226601002f408d56e81837ab69b8d4e | CONTRIBUTOR | 13221727 | https://github.com/pydata/xarray/pull/6144 |
Links from other tables
- 1 row from pull_requests_id in labels_pull_requests