exit() instead of exception
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Search the C sources for exit(1) and the duplicate-coordinate condition described in the issue; start by tracing how that path is exposed to the Python program. Add coverage for conflicting input triples and verify the program can handle the reported failure without terminating.
Written by the indexing model from the issue text.
Description
When "two input triples have the same x/y coordinates but different data values" calls exit(1) instead of raising exception. This causes whole python program to exit suddenly without chances to handle the exception..
- Dominant language
- C
- Stars
- 17
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from matplotlib/natgrid
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
matplotlib/natgrid#1 ·
All issues in matplotlib/natgrid
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
kovidgoyal/kitty#10516 ·
-
libc
Difficulty 2/5 1-2 days Newbie friendliness 76/100
llvm/llvm-project#225506 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Status: Waiting triage Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
nanoframework/Home#1857 ·
-
bug
Difficulty 2/5 Half a day Newbie friendliness 82/100