ENH: np.linalg.eig doesn't process the SIGINT signal
Open
Nobody has claimed this yet.
01 - Enhancement
component: numpy.linalg
- Dominant language
- Python
- Stars
- 32.8k
- Forks
- 12.8k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 197
Description
Ctrl-C doesn't have any effect.
py27-numpy-1.13.3_3,1 on FreeBSD-11.1
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 at the np.linalg.eig entry point and reproduce the Ctrl-C behavior in the reported py27-numpy-1.13.3_3,1 environment on FreeBSD 11.1. Confirm that SIGINT is not handled during the eig operation; done means Ctrl-C produces the expected interruption instead of having no effect.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100