-
Notifications
You must be signed in to change notification settings - Fork 279
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
Yet Another Jedi Exception : ) #223
Comments
Hi @liavkoren It's not the cleanest solution, but otherwise I have to keep adding exceptions for everything that Jedi will throw. |
Oh, just saw this. Would you like me to pull the commit and check it locally? |
Okay, I'm tots confused. I cloned the repo and pip installed -e, but I can't reproduce the jedi error even on |
Ok. No problem. I'll probably merge it anyway. These Jedi errors are pretty annoying, and right now, I don't have a good way to log what's going wrong without disturbing the end user. |
Thanks! |
Note: the exception happens immediately on typing the period in
(a - b > 0).
numpy==1.10.4
prompt-toolkit==1.0.15
jedi==0.11.0
I deeply love ptipython (it's my default python repl) and, you know, god[s]/time-management willing, I'm happy to try and help.
It's not super rare for me to run into Jedi exceptions. Overall, those aren't actually a big deal, but what is kind of a drag is then not having access to autocomplete for the rest of the life-span of the parent ptpython session. I'm assuming Jedi is being run in a child thread, and when it hits an unhandled exception, it takes autocomplete out. How much of a PITA would it be for a new Jedi to be created when that happens?
The text was updated successfully, but these errors were encountered: