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
I'm following the instructions posted in this Community forum blog post to run werkzeug profiler in my Dash application to identify performance bottlenecks.
It doesn't work with python version 3.12, receiving error:ValueError: Another profiling tool is already active. I'm not running any other profiler in the application and I've tried disabling Linux profiler (python app.py -X perf 0)
It works fine with python <=3.11
This issue would need to be fixed upstream in Werkzeug (pallets/werkzeug#2909 ) or cpython (python/cpython#110770 ). As in both cases it's not planned, we might consider updating our recommendations for profiling instead of trying to change anything in core Dash.
Describe your context
I'm following the instructions posted in this Community forum blog post to run
werkzeug
profiler in my Dash application to identify performance bottlenecks.It doesn't work with python version 3.12, receiving error:
ValueError: Another profiling tool is already active
. I'm not running any other profiler in the application and I've tried disabling Linux profiler (python app.py -X perf 0
)It works fine with python <=3.11
pip list | grep dash
:Describe the bug
I receiving the error
ValueError: Another profiling tool is already active
when running the application with python version 3.12.Expected behavior
It should work as it does with python<=3.11
The text was updated successfully, but these errors were encountered: