Skip to content
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

varInspector keeps variables persistent after using %reset magic #1014

Closed
edridgedsouza opened this issue Jun 27, 2017 · 3 comments · Fixed by #1016 or zenotech/zCFDSuperBuild#99
Closed
Labels

Comments

@edridgedsouza
Copy link

If you reset the kernel with the %reset magic command, all of the previous variables are still present with their old values in the variable explorer. This doesn't appear to happen when the variables are individually deleted with del

@jfbercher
Copy link
Member

Reproducible and Interesting.
Even new variables are not listed. I will look at what does %reset; but perhaps that it creates a new namespace and that the last one is still accessible. This would mean that perhaps varInspector needs to catch the %reset magic and restarts itself in that case;

@jfbercher jfbercher added the bug label Jun 28, 2017
jfbercher added a commit to jfbercher/jupyter_contrib_nbextensions that referenced this issue Jun 30, 2017
@jfbercher
Copy link
Member

The hypothesis in my previous comment (that %reset may create a new namespace) was wrong.

What happened was simply that some hidden variables and functions used by varInspector (to list all variables used by the current kernel) were cleared by the %reset, and therefore varInspector failed. In #1016 , the state of the refresh operation is checked, and in case of error (which occurs if the variables/functions used by varInspector are cleared), the extension is reinitialized.

@jfbercher
Copy link
Member

Should be fixed by #1019

jfbercher added a commit that referenced this issue Jul 14, 2017
[varInspector] Fix #1014 and #1015 - reload on  %reset magic and fix print on python2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
2 participants