with zmq disabled, prompt to install notebook package shows twice when cancelled
See original GitHub issue- add the setting
"jupyter.disableZMQSupport" : true
to disable zmq - open a .py file with a
#%%
cell and set the active interpreter to an environment without the notebook package installed. - run the cell and cancel the install prompt that appears.
Actual: Prompt reappears immediately (just once), and needs to be cancelled again
Issue Analytics
- State:
- Created a year ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Messaging in Jupyter — jupyter_client 7.4.8 documentation
This document explains the basic communications design and messaging specification for how Jupyter frontends and kernels communicate. The ZeroMQ library ...
Read more >Jupyter Notebook Documentation - Read the Docs
The landing page of the Jupyter notebook web application, the dashboard, shows the notebooks currently available in.
Read more >Jupyter Installation - python - Stack Overflow
While I was downloading jupyter and trying to open the jupyter notebook. Errors below were shown to me instead. Traceback (most recent call...
Read more >Setting up IPython Notebook on Windows - Christian Richardt
So let's get started on how to install IPython Notebook on Windows 7. ... Run ipython notebook in a command line. If you're...
Read more >OpenModelica User's Guide
OpenModelica has a package manager that can be used to install and update ... Enable Line Wrapping – Enable/Disable the line wrapping.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@rchiodo this is slightly different, the problem is we’re handling the error in two places. First we handle the error in the kernel startup code (wrapKernelMethod), and then we also handle the errors the code watcher. I’m going to implement a simple fix for this (if the error object has already been handled once, then the next time we attempt to handle it, it will result in a noop)