pymc-devs / pymc-devs/pytensor
Can we automate transfer of stack traces?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 644
- Forks
- 208
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 16
Description
Description
#735 shows how the current interface to copy stack traces during rewrites look like. It's verbose and easy to forget.
There is/was a special mode/flag to check variables always have a stack trace, but I guess we're not running with it.
Can we automate this kind of behavior (at least for node rewriters)?
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 reading issue #735 to understand the current interface for copying stack traces during rewrites, then locate the node rewriters and the existing mode or flag intended to check stack traces. Done means stack-trace transfer is automated for at least node rewriters and the behavior is verified without requiring the current verbose interface.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100