-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Some issues with dedicated consoles #4856
Comments
That's an easy fix.
This probably happens the first time you run in a dedicated console. Errors always appear for me afterwards.
This has been the default behavior for all Spyder history, i.e. changing the cwd to the current file directory on execution, so I'm reluctant to change it. We are now simply reflecting that in our UI, which is what most people wanted. |
Yes, indeed, but this is still a bug, users should not need to run a script twice to see what failed.
It may be, but it provides a very annoying experience |
Sure, I just wanted to verify that it only happens once.
Please propose an alternative. Just complaining is not constructive. |
I guess I have to adapt my workflow. If I think of something, will let you know |
Yes, I also find annoying that the cwd changes too frequently |
I agree with @rlaverde and @ccordoba12 |
Ok, I'll work on this one for 3.2.2 |
The dedicated run in ipython console has some issues.
1.) When a script runs, there is a flash for a moment of

before it goes blank again, but then
2.) any output (prints, exceptions) that may or may not occur in the script never show up
3.) Changing the working directory (file explorer, global working directory) every time a new scripts runs turns out to be a very annoying behavior, and I think we should rethink that
The text was updated successfully, but these errors were encountered: