-
Notifications
You must be signed in to change notification settings - Fork 146
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
Jupyter-console incompatible with prompt-toolkit 2.0.2 #158
Comments
+1 |
Same issue here. Hope it can be fixed soon. |
Jupyter console needs some love. Most of the same work has been done in ipython/ipython#11177, if any of you have the time, feel free to send PRs. |
Same issue |
Oddly, it was working fine for a few weeks and suddenly today after rebooting, I got that same error. @blfuentes 's temporary solution worked perfectly. This is the command:
|
Same here.. And it seems to be interfering with my jupyter notebook (via ipython) |
When will this be fixed? Its been more than one month that this bug prevents jupyter from running. |
When someone gets to it. You can continue using Jupyter with prompt_toolkit 1.0.x in the meantime, so it's not high priority. |
More especially, this is an open source project that is mostly developed by volunteers on their own time, which is one of resource we miss most. You can also help us by contributing to the project in other way (PR reviews, documentation, managing mailing list, social media, responding to other issues) which should free up time for more knowledgeable people to take care of complex issues. Thanks |
Ok, I see. It is not a hi-priority, and this is a volunteer project. You assume that everybody knows python, knows how to hack jupyter code (and provide patches), and that the operating system is not pushing any updates. |
Need to coordinate the release of a new jupyter-console with ipython, otherwise they each want different versions of prompt_toolkit. If this is still an open issue, I'll port jupyter_console to prompt-toolkit later today. |
Ok, cool! I made a couple of comments over there. I see why you want these released first... dependencies! |
And that isn't just "someone"... that's @s-weigand ! |
Same here... Do NOT want to downgrade... |
I think I am getting a different flavor of this problem. First attempt to install
But when I run
I get the following
Second attempt to install
I get this
System Specifications
|
I just release IPython 7.0 that does support prompt_toolkit 2, now we can review the linked PR, merge it and deployed a new version of QtConsole. There are just a dependencies between tasks that need to be taken care of... Help welcome in particular any task 9+ in this list still need someone to check manually that it has been done: https://ipython.readthedocs.io/en/stable/coredev/index.html#update-milestones-on-github |
@Carreau regarding your first comment in the issue: I thank all the voluntary effort that you do across the Jupyter ecosystem, and acknowledge that Jupyter devs get lots of undeserved whining from impatient users (I saw another thread where someone was using However, "feel free to send PRs" not only is hardly a useful explanation of what exactly needs to be done to port jupyter_console to prompt_toolkit 2.0: it also deviates the attention from the main user-facing issue, which is that people get broken installations. jupyter_console is a package that most users do not use directly, but it gets installed when people do $ jupyter console
Traceback (most recent call last):
File "/home/juanlu/.miniconda36/envs/propan36/bin/jupyter-console", line 7, in <module>
from jupyter_console.app import main
File "/home/juanlu/.miniconda36/envs/propan36/lib/python3.6/site-packages/jupyter_console/app.py", line 26, in <module>
from jupyter_console.ptshell import ZMQTerminalInteractiveShell
File "/home/juanlu/.miniconda36/envs/propan36/lib/python3.6/site-packages/jupyter_console/ptshell.py", line 21, in <module>
from IPython.core import page
File "/home/juanlu/.miniconda36/envs/propan36/lib/python3.6/site-packages/IPython/__init__.py", line 55, in <module>
from .terminal.embed import embed
File "/home/juanlu/.miniconda36/envs/propan36/lib/python3.6/site-packages/IPython/terminal/embed.py", line 16, in <module>
from IPython.terminal.interactiveshell import TerminalInteractiveShell
File "/home/juanlu/.miniconda36/envs/propan36/lib/python3.6/site-packages/IPython/terminal/interactiveshell.py", line 20, in <module>
from prompt_toolkit.formatted_text import PygmentsTokens
ModuleNotFoundError: No module named 'prompt_toolkit.formatted_text' In my opinion "jupyter_console is incompatible with IPython 7 at the moment because it's not yet ported to prompt-toolkit 2, please upgrade prompt-toolkit and you will be able to safely use IPython and Jupyter Notebook (at the cost of breaking jupyter_console) while someone does the port." would have been a much more useful comment. Even a hotfix of the jupyter metapackage restricting the versions would be a better temporary solution to this problem: https://github.com/jupyter/jupyter/blob/563951c60d66118a79fa397efb410280f3ce4db7/setup.py#L26-L33 (See also #166) Please take this as constructive criticism, I love what you folks are doing and hope that you continue to enrich this wonderful project <3 |
@Juanlu001, thanks for the constructive criticism, I'll take it into account. I just want to no that this issue was open before IPython 7 was released, and it was unknown (at the time) how we would handle the transition. It is often also relatively hard to balance giving the right amount of information. In general, many project are highly under-maintained in Jupyter, and we may even miss that some people have contributed a lot, and should have received more permission on repo/gotten commit right, or recognition. I have some names in mind, but don't want to say anything without consulting the rest of the team. When this is the case, please feel free to remind us of so like @Juanlu001 did, and we'll tust the community and try to foster collaboration. Would anyone be willing to send a PR similar to this one from IPython to this repo, in order to allow anyone the ability to label and close issue, so that there is less bottleneck on the core devs ? Thanks ! |
When doing a fresh setup of pb-exercises, I’m seeing a problem with jupyter. It isn’t able to print ‘hello world’. This appears to be related to an incompatibility of IPython 7.0.1 and jupyter-console which depend on different versions of prompt_toolkit See jupyter/jupyter_console#158 This is a temporary fix for the problem, which can be removed once the jupyter issue is resolved.
Can someone explain how we can run Jupyter if we are willing to downgrade? |
There is a conflict of versions for dependency 'prompt-toolkit', see HDI-Project#12 and jupyter/jupyter_console#158. To resolve it, I tried to specify the versions of ipython & jupyter-console.
This works for me in Ubuntu 18.04. |
You also may need to do this: |
@ldmtwo worked for me thanks ! |
@artgoldberg thanks, it worked! |
|
I have the same issue. Have read all comments here but still can't get rid of the error message. Using Ubuntu 18.04. Is there a known reproducible way to make it work on this OS? |
Thank you man, this worked for me |
|
If this hasn't been fixed yet, may I take my hand at working on a solution? |
Of course, and sorry if we can be slow to review. Feel free to ping us if necessary. |
worked just fine for me with no sudo too. |
The new version of prompt-toolkit(< 2.0) is 1.0.16(update Apr 12, 2019) |
Hi future readers, per this: Using this version works (I've also confirmed) Presumably you are using an old version, but if you are just looking to get something running... |
|
Try pip install ipython --upgrade --user |
Also, worked for me, Thanks |
After updating the prompt-toolkit package to the version 2.0.2 I get the following error message :
jupyter-console 5.2.0 has requirement prompt-toolkit<2.0.0,>=1.0.0, but you'll have prompt-toolkit 2.0.2 which is incompatible.
Then if I start a jupyter notebook the message "kernel died" is appearing all the time with this output
I downgraded the prompt-toolkit to the version 1.0.15 and jupyter worked again.
Python 3.6.5
jupyter 1.0.0
jupyter-client 5.2.3
jupyter-console 5.2.0
jupyter-core 4.4.0
ipython 6.4.0
The text was updated successfully, but these errors were encountered: