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

Some issues with dedicated consoles #4856

Closed
goanpeca opened this issue Jul 29, 2017 · 8 comments
Closed

Some issues with dedicated consoles #4856

goanpeca opened this issue Jul 29, 2017 · 8 comments

Comments

@goanpeca
Copy link
Member

goanpeca commented Jul 29, 2017

The dedicated run in ipython console has some issues.

1.) When a script runs, there is a flash for a moment of
screen shot 2017-07-29 at 11 21 25
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

@ccordoba12
Copy link
Member

ccordoba12 commented Jul 29, 2017

When a script runs, there is a flash for a moment of

That's an easy fix.

any output (prints, exceptions) that may or may not occur in the script never show up

This probably happens the first time you run in a dedicated console. Errors always appear for me afterwards.

Changing the working directory (file explorer, global working directory) every time a new script runs turns out to be a very annoying behavior, and I think we should rethink that

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.

@goanpeca
Copy link
Member Author

This probably happens the first time you run in a dedicated console. Errors always appear for me afterwards.

Yes, indeed, but this is still a bug, users should not need to run a script twice to see what failed.

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.

It may be, but it provides a very annoying experience

@ccordoba12
Copy link
Member

Yes, indeed, but this is still a bug, users should not need to run a script twice to see what failed.

Sure, I just wanted to verify that it only happens once.

It may be, but it provides a very annoying experience

Please propose an alternative. Just complaining is not constructive.

@goanpeca
Copy link
Member Author

I guess I have to adapt my workflow. If I think of something, will let you know

@ccordoba12
Copy link
Member

We could change the default option to not change the cwd on evaluation, which I also think is a saner default.

@rlaverde, @dalthviz, @andfoy, what do you think?

@rlaverde
Copy link
Member

We could change the default option to not change the cwd on evaluation, which I also think is a saner default.

Yes, I also find annoying that the cwd changes too frequently

@ccordoba12 ccordoba12 changed the title Run in dedicated (ipython) console Some issues with dedicated consoles Jul 30, 2017
@andfoy
Copy link
Member

andfoy commented Jul 31, 2017

I agree with @rlaverde and @ccordoba12

@ccordoba12
Copy link
Member

Ok, I'll work on this one for 3.2.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants