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

Interactive mode hangs: Windows 10, VS 2019, 64 bit #5233

Closed
sriksrid opened this issue Apr 12, 2019 · 3 comments
Closed

Interactive mode hangs: Windows 10, VS 2019, 64 bit #5233

sriksrid opened this issue Apr 12, 2019 · 3 comments

Comments

@sriksrid
Copy link

sriksrid commented Apr 12, 2019

Hi

I have tried two different installations of Python 3 (Aanconda3 2019.03, and a barebones 3.7 with ipython, pandas, matplotlib installed) on Windows 10 (clean install). In both cases, if I set the checkbox "Use IPython interactive mode", the interactive window hangs as soon as I type any command (or even no command, just an enter to increment the counter). Resetting the process outputs three lines:

Resetting Python state.
[IPKernelApp] WARNING | Parent appears to have exited, shutting down.
The interactive Python process has exited.
>> {I press enter}
In [2]: {I press enter}
hangs.

I also noticed that the module dropdown (in non IPython mode) shows "main", while the IPython mode doesn't show this drop down at all. How should I use the IPython interactive mode with VS 2019?

Thanks.

@huguesv
Copy link
Contributor

huguesv commented Apr 12, 2019

Thanks for letting us know about this.

It works with Anaconda 2018.12 but now with 2019.03 I see the behavior you described.

@huguesv
Copy link
Contributor

huguesv commented Apr 12, 2019

The problem appears when using pyzmq==18.0.1 (currently the latest)

You can downgrade that package to 17.1.2 or 17.1.3 and things appear to work again.

@sriksrid
Copy link
Author

Thank you. That works great.

@qubitron qubitron added this to the April 2019.2 milestone Apr 16, 2019
bschnurr added a commit that referenced this issue Apr 23, 2019
- Both execute(..) and get_shell_msg(..) act on the same shell socket and having a blocking call to get_shell_msg(..) no longer works with the newer pyzmq.
- temporary fix was to downgrade pyzmq to 17.1.3
- Changed get_shell_msg(..) to use a timeout instead of blocking.

related to bug  #5233
bschnurr added a commit that referenced this issue Apr 23, 2019
 fix for repl hang when using  with pyzmq => 18.0.0

- Both execute(..) and get_shell_msg(..) act on the same shell socket and having a blocking call to get_shell_msg(..) no longer works with the newer pyzmq.
- temporary fix was to downgrade pyzmq to 17.1.3
- Changed get_shell_msg(..) to use a timeout instead of blocking.

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

No branches or pull requests

4 participants