You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, py.test --pdb are not optimal for generative tests, as the backtrace goes into the part of nose's code that runs the generator, instead of going into the generator itself. I'd guess it should be possible (if somewhat hackish) to retrieve the traceback of the generator instead (gen.gi_frame) and stitch it into the current traceback, so that the generator's frame becomes accessible in pdb via up.
Currently,
py.test --pdb
are not optimal for generative tests, as the backtrace goes into the part of nose's code that runs the generator, instead of going into the generator itself. I'd guess it should be possible (if somewhat hackish) to retrieve the traceback of the generator instead (gen.gi_frame
) and stitch it into the current traceback, so that the generator's frame becomes accessible in pdb viaup
.Thoughts?
(crossposted as nose-devs/nose2#260)
The text was updated successfully, but these errors were encountered: