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
The submodule werkzeug.debug.tbtools as of version 2.0 upwards no longer has the classes Frame, Traceback, Line, therefore this line fails:
fromwerkzeug.debug.tbtoolsimportTraceback, Frame, Line# ImportError: cannot import name 'Traceback' from 'werkzeug.debug.tbtools'
Rolling back to werkzeug==2.0 crashes flask.
werkzeug has DebugFrameSummary, DebugTraceback and a smattering of variable for line as far I can tell. cf.werkzeug.debug.tbtools as they do not look the same I did not do a monkeypatch as working around the error reporting is not an issue for me as I can happily blank out the error catching in my internal production app.
I see in setup.py the project status is Development Status :: 3 - Alpha, so wanted to ask if it's actually Development Status :: 7 - Inactive — the werkzeug change happened over a year ago.
The text was updated successfully, but these errors were encountered:
The submodule
werkzeug.debug.tbtools
as of version 2.0 upwards no longer has the classesFrame
,Traceback
,Line
, therefore this line fails:Rolling back to
werkzeug==2.0
crashes flask.werkzeug has
DebugFrameSummary
,DebugTraceback
and a smattering of variable for line as far I can tell. cf.werkzeug.debug.tbtools as they do not look the same I did not do a monkeypatch as working around the error reporting is not an issue for me as I can happily blank out the error catching in my internal production app.I see in
setup.py
the project status isDevelopment Status :: 3 - Alpha
, so wanted to ask if it's actuallyDevelopment Status :: 7 - Inactive
— thewerkzeug
change happened over a year ago.The text was updated successfully, but these errors were encountered: