IronLanguages / IronLanguages/ironpython3
Exception traceback not preserved
Open
Nobody has claimed this yet.
What's New In Python 3.0
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 316
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 1
Description
try:
raise Exception
except Exception as e:
raise e
should give
Traceback (most recent call last):
File "<stdin>", line 4, in <module>
File "<stdin>", line 2, in <module>
Exception
but gives
Traceback (most recent call last):
File "<stdin>", line 4, in <module>
Exception
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 reproducing the exception-handling example from the issue and compare IronPython's traceback with the expected CPython-style traceback. Trace the implementation of raise e and traceback construction, then add coverage for this example and verify that both traceback frames are preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100