-
Notifications
You must be signed in to change notification settings - Fork 89
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
Crash on unicode scripts #43
Comments
Can you try dev version of Jedi? You need to clone https://github.com/davidhalter/jedi, check out |
The dev version of jedi gives me the same behaviour. I ran the following commands:
I still get the traceback above. |
Hmm... Can you try to full stack trace from Python? You can get it by playing with the option for jediepcserver.py: Or pahapse the easiest (becase it is documented) way to do is to run in debug mode: Also please run |
jedi version:
I'm not sure how to get a stack trace. I ran
in a shell. I can then see the port in the jedi-port.log file. However, it's not clear to me how to get Emacs to talk to this jediepcserver instance. I also tried executing |
Here is how to use jedi:toggle-debug-server:
|
Perfect. Here's the traceback:
|
Thank you. I think now I know how to reproduce the problem in my machine. But I don't have enough time right now so it may take sometime to fix. |
It turned out to be sexpdata's bug. Upgrade sexpdata then it should be fine. If you use |
Great, I can confirm this works. Could you please update |
Thanks. Good point. I will do it. |
Given the following Python script:
Putting point on function and editing it gives me:
I believe my emacs-jedi setup is correct, it generally works well. This bug is just a slight annoynce when I'm editing this file, since my minibuffer keeps flashing up.
The text was updated successfully, but these errors were encountered: