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
If I encounter an error and this script doesn't run to completion, and I try to run again (after fixing the problem but that's not required here), I encounter this error at the pr.enable() line.
ValueError: Another profiling tool is already active
At this point, even if I run pr.disable() or even del pr, this error never goes away. The only thing that works is to restart the kernel itself.
Is this a bug? Is this a bad practice that I should not do (if so, what's the standard practice?)?
The text was updated successfully, but these errors were encountered:
Okay I skipped a couple of steps and hence may have filed this in the wrong location - I'm following the Spyder troubleshooting guide and I first got it in Spyder. Then I tried qtconsole and got the error there as well, which is why I opened this issue.
But just now I tried it in IPython and again got the error. So now I ran it in the Python interpreter using exec(open('mainrunner.py').read()) and still get the same problem - the profiling state cannot be disabled, reset, removed or anything else seemingly. Obviously running an entirely different instance of Python with python mainrunner.py does not show this problem.
What should I do? It feels like I'm doing something wrong here.
In my script, I use profiling to keep track:
If I encounter an error and this script doesn't run to completion, and I try to run again (after fixing the problem but that's not required here), I encounter this error at the
pr.enable()
line.ValueError: Another profiling tool is already active
At this point, even if I run
pr.disable()
or evendel pr
, this error never goes away. The only thing that works is to restart the kernel itself.Is this a bug? Is this a bad practice that I should not do (if so, what's the standard practice?)?
The text was updated successfully, but these errors were encountered: