highlight user frames in interactive debugger #1421
Adds a new
Library frames are detected by comparing their filename to all paths returned by
If the detection thinks all or no frames are library code, it reverts to the old behavior of highlighting everything. This could happen, for example, if a project is installed in its virtualenv without using
Unfortunately, virtualenv ships its own
Due to the issue with virtualenv, which is what tox uses, I couldn't think of a reliable test for this, so this remains "untested" for now, although manual testing showed it working as expected.
The text was updated successfully, but these errors were encountered: