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
Functionality for my projects are distributed across multiple files that I import at the top of my files. When I make changes to those referenced files and then call code in a separate file that is using those changes, the new version of the file will not be used. The way around it seems to be clicking to debug the whole file (I'll set a breakpoint in my import statements so my data doesn't need to be loaded again) so that the referenced modules are reloaded, then running the relevant import statements for the changed files. This was not necessary in prior releases of Spyder, is this an intentional change of functionality or a bug? I would expect that if I make a change to any file, the next time I run a piece of code referencing that changed file, that the latest changes will be used. I have the UMR enabled, but that only seems to be applying when I try to debug the whole file instead of just rerunning a cell or line of code.
This functionality returns when enabling the IPython autoreload setting which maybe seems to have been disabled in this new version of Spyder based on previous documentation:
Perhaps it would be good to either notify people of this change or include it in the new documentation (It is currently not mentioned).
ccordoba12
changed the title
Spyder 6 - Running cells or lines of code will not use latest changes in imported module files
Spyder 6 - %autoreload magic not loaded by default on Windows
Sep 5, 2024
This functionality returns when enabling the IPython autoreload setting which maybe seems to have been disabled in this new version of Spyder
Thanks for finding the cause of the problem! We inadvertently disabled that magic on Windows, but we'll fix that in 6.0.1, to be released in a couple of weeks.
Description
What steps will reproduce the problem?
Functionality for my projects are distributed across multiple files that I import at the top of my files. When I make changes to those referenced files and then call code in a separate file that is using those changes, the new version of the file will not be used. The way around it seems to be clicking to debug the whole file (I'll set a breakpoint in my import statements so my data doesn't need to be loaded again) so that the referenced modules are reloaded, then running the relevant import statements for the changed files. This was not necessary in prior releases of Spyder, is this an intentional change of functionality or a bug? I would expect that if I make a change to any file, the next time I run a piece of code referencing that changed file, that the latest changes will be used. I have the UMR enabled, but that only seems to be applying when I try to debug the whole file instead of just rerunning a cell or line of code.
Versions
Dependencies
The text was updated successfully, but these errors were encountered: