BUG: np.interp(nan, x, y) doesn't return nan when len(x)=1
Open
Nobody has claimed this yet.
00 - Bug
54 - Needs decision
- Dominant language
- Python
- Stars
- 32.8k
- Forks
- 12.8k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 197
Description
Reproducing code example:
import numpy as np
np.interp(np.nan, [1], [2])
returns 2.0 while nan is expected.
It returns nan correctly when len(x) > 1
np.interp(np.nan, [1, 1], [2, 2])
My numpy version: 1.15.3
Related issue: https://github.com/numpy/numpy/issues/605
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the reported np.interp(np.nan, [1], [2]) example and compare it with the len(x) > 1 case. Trace the np.interp entry point to identify why the single-element input returns 2.0, then add or update coverage for the expected nan result and run the relevant NumPy tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100