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

Remove the Python console #4524

Closed
10 tasks done
ccordoba12 opened this issue May 31, 2017 · 2 comments
Closed
10 tasks done

Remove the Python console #4524

ccordoba12 opened this issue May 31, 2017 · 2 comments

Comments

@ccordoba12
Copy link
Member

ccordoba12 commented May 31, 2017

This issue describes our reasons to remove the Python console from Spyder:

  1. Broken on Windows: Executing code on it usually doesn't return the prompt. The situation is worst when Matplotlib integration is turned on because you have to press Enter several times to get a prompt back.
  2. Matplotlib integration: Nowadays Matplotlib is tightly integrated with IPython and it's very difficult to have a different console with good Matplotlib support. Right now the only backend we are able to support in our Python consoles is the Qt one (not even Tk works!), and (as said above) it's broken on Windows.
  3. Different implementations: We are a small project and don't have the resources nor the time to maintain two consoles with very different implementations (we're also in charge of qtconsole).
  4. Debugging: It's not possible to detect when a Python console is running a debugging session, so we can't adapt certain functionality for debugging only (e.g. disabling buttons on the Debug toolbar).
    Besides, we plan to improve debugging in Spyder 4 by creating an IPbd kernel, so that users can run multiline code from the Editor, have code completion and history browsing while debugging. Unfortunately, this is something we can't support in the Python console.
  5. History log: The history log is semi-broken because we can't make it work reliably for both consoles.
  6. Not testable: It's not easy to add tests for the Python console because you can't tell for sure when the console is up and ready nor when it has finished a computation. That's why there are no tests for it right now.

TODO:

@koradir
Copy link

koradir commented Jun 15, 2017

Will "Add Execute in a dedicated console option to the IPython console." once implemented still resolve issues like
https://stackoverflow.com/questions/38042329/python-kivy-app-running-only-once
?

@ccordoba12
Copy link
Member Author

Yes, I think so because the kernel will be restarted every time on a dedicated console.

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

2 participants