Open blueyed opened 6 years ago
GitMate.io thinks possibly related issues are https://github.com/pytest-dev/pytest/issues/1996 (Warnings handling), https://github.com/pytest-dev/pytest/issues/132 (Pygmentize native tracebacks), https://github.com/pytest-dev/pytest/issues/2684 (review warning stacklevels), https://github.com/pytest-dev/pytest/issues/1370 (Print out pytest-warnings?), and https://github.com/pytest-dev/pytest/issues/2332 (What is multicall warning?).
Would also be nice to automatically call pdb on warnings.
-W error --pdb
works, but only for the first warning.
Maybe something like -W pdb
could be added, which would behave similar to -W error --pdb
, but continue afterwards instead of stopping.
Will this not be implemented after all?
As per https://github.com/carltongibson/django-filter/pull/903#issuecomment-394865805 it might be useful to display tracebacks with warnings.
Since this makes the warnings section very verbose, this should become a separate option probably, or could be controlled through
--verbose
maybe.