-
Notifications
You must be signed in to change notification settings - Fork 201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Profiling once active/enabled cannot be deactivated/disabled #614
Comments
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 What should I do? It feels like I'm doing something wrong here. |
Hello? Bump! |
I think the only solution is to restart the kernel after fixing the error to get rid of the previous profiling session and start all over again. |
@ccordoba12 This sounds bad — what is the point of the |
I don't know what the
As long as there is a profiling session active, you can't start another one. And the only way to do that is by restarting the kernel, I guess. |
Noted. Since it sounds pretty wrong to me, where would you recommend I go next to resolve ambiguity in the "I guess" part of your answer? https://github.com/ipython/ipython ? Thanks! |
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: