pytest-dev / pytest-dev/pytest
Option to hide pluggy even with `--full-trace` is used
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 14.5k
- Forks
- 3.4k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 35
Description
Hi. Without any option the traceback that produces pytest is quiet enough. Sometimes I want to see what is going on upper in the call graph, without calling pdb, so I use --full-trace --showlocals options. This shows me what I want to see, but much more too, as it displays the whole pluggy traceback.
I suggest adding an option (something like --verbose-traceback), or editing the --full-traceback option (something like --full-traceback=half), so it is possible to have the full user-written traceback but not the pytest internal stuff.
What do you think?
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 tracing pytest's --full-trace and --showlocals option handling and how pluggy frames are included in reported tracebacks. Decide which behavior should distinguish user-written from pytest-internal frames, then add coverage showing the selected traceback output without pluggy internals.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100