How should try-except clauses be modeled?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 681
- Forks
- 65
- PR merge metrics
- No merged PRs in 30d
Description
From @sigmavirus24
Actually now that I think of a more complex example
def f():
try:
function_one(1)
function_two(arg)
except TypeA:
print(2)
except TypeB:
print(3)
else:
print(4)
finally:
if x:
print(5.1)
else:
print(5.2)
I see that actually you could branch to any of the except clauses from either of the statements in the try block. I still don't think that the except branches coming from the try block is correct so maybe something like
-----------------> except clause 1
/ / \
try -> function_one -> function_two ----> else
\ \ /
-----------------> except clause 2
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.
Research direction
The issue provides a nested try/except/else/finally example but names no files, tests, or entry points. First inspect the existing control-flow modeling for try statements and discuss the intended graph semantics. Done means an agreed behavior for the example, followed by implementation and regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100