Closed bsesar closed 2 years ago
Hi @bsesar thank you for the feedback! I'm not totally sure but maybe this could be caused due to the retrieval of the kernel namespace when executing something to show it from in the Variable Explorer. Pinging @ccordoba12 and @impact27 (maybe them have some ideas about what could be happening here)
Hi @dalthviz. Is it possible to somehow turn off Variable Explorer? I find the above behavior quite annoying.
Could the above issue be related to the fix for #16844? Back in 2020 I reported an issue (#14265) related to Dask and Variable Explorer and that issue was fixed in 5.3.0.
Thanks for the info and references @bsesar ! Those were the issues I had in mind when thinking about possible causes for this.
To turn off the Variable Explorer you can go to Preferences > Plugins
and uncheck Variable explorer
:
After applying the settings you will need to restart Spyder:
Let us know if that helps!
Hi @dalthviz. After I turned off Variable Explorer, the unwanted triggering of Dask tasks stopped. Thanks! :-)
Glad the workaround worked for you @bsesar !
Note: The call to the kernel triggering Dask tasks is caused by a call to get_var_properties
when doing a call to refresh_namespacebrowser
(which is called after any console execution)
Issue Report Checklist
conda update spyder
(orpip
, if not using Anaconda)jupyter qtconsole
(if console-related)spyder --reset
Problem Description
For some reason, Spyder triggers re-execution of Dask tasks that already finished. This behavior is not present when executing the code in Python or IPython. Restarting the Dask cluster does not remove these tasks from memory and they keep re-executing. The only way to remove tasks is to restart Spyder.
What steps reproduce the problem?
What is the expected output? What do you see instead?
I expect only the relevant Dask code to be executed. When executing the above code in Python or IPython, tasks associated with df Dask DataFrame do not get executed.
Versions
Dependencies