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
Originally reported by: Vyacheslav Rafalskiy (BitBucket: s4g, GitHub: s4g)
In some use cases, especially in functional testing, the pytest_configure(), pytest_sessionstart() and other hooks can be loaded with heavy setup code, which can fail in many different ways. If exceptions in such code are reinterpreted, as is the case in pytest 2.0.2, the important pre-formatted messages and traces are lost, or at least disfigured by long listings with every line prepended with 'INTERNALERROR>'.
It is desirable to be able to avoid such reinterpretation with a command-line option or other means.
Presently, I use the following monkey-patch as a workaround:
Original comment byholger krekel (BitBucket: hpk42, GitHub: hpk42):
you can try out the fix with "pip install -U pytest -i http://pypi.testrun.org" - traceback will be "native" and it's also possible to specify "--fulltrace" in order to get a full traceback.
Originally reported by: Vyacheslav Rafalskiy (BitBucket: s4g, GitHub: s4g)
In some use cases, especially in functional testing, the pytest_configure(), pytest_sessionstart() and other hooks can be loaded with heavy setup code, which can fail in many different ways. If exceptions in such code are reinterpreted, as is the case in pytest 2.0.2, the important pre-formatted messages and traces are lost, or at least disfigured by long listings with every line prepended with 'INTERNALERROR>'.
It is desirable to be able to avoid such reinterpretation with a command-line option or other means.
Presently, I use the following monkey-patch as a workaround:
The text was updated successfully, but these errors were encountered: