Option to hide pluggy even with --full-trace is used

[azmeuk]

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?

[RonnyPfannschmidt]

my surrounding idea would be to have "collabsile" framework parts for tracebacks, so stuff like django orm, sqlalchemy, pytest/pluggy , flask&co as well as helper libraries can be hidden by default and shown on demand

however i dont think i will get to work on that part of pytest this year

[azmeuk]

I love this idea, I just realized you mentioned it in #283
Until this is implemented, what do you think of the idea to add an option that would show a full-trace, but without the pluggy parts?

[RonnyPfannschmidt]

its a nice idea - when implementing it, one could take a look at enabling some extra filtering based on toplevels to go towards #283 (aka instead of jsut fintering pluggy, being able to filter more based on a extra option)

--traceback-skip-toplevel=pluggy,sqlalchemy,django.orm might be a nice hack