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
This came first in scipy/scipy#13116 , might help cooking up a standalone test case.
Once there is a test, it'll be easier to decide if this can be merged with --continue_on_failure in the plugin layer.
and it indeed seems to match: with --doctest-continue-on-failure the traceback has four exceptions (as expected for name_error_after_exception=True); without it we only get one.
So need to golf sync the DTConfig setting and the pytest setting:
if the pytest switch is on, it overwrites the DTConfig one (maybe emit a warning on mismatch)
if the pytest switch is off, it is synced from DTConfig.
However, this would require to multiple inherit PytestDTRunner from both DebugDTRunner (which it does now) and pytest's PytestDoctestRunner.
Does not seem worth it TBH.
Also, the PytestDTRunner inherits from DebugDTRunner, so it stops after the first exception anyway. Also, DebugDTRunner overrides all logic from nameerror_after_exeption.
#87 (comment) please make sure that this test passes with the plugin
Originally posted by @ev-br in #87 (comment)
The text was updated successfully, but these errors were encountered: