-
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
deferred error : (error ""AttributeError("'Definition' object has no attribute 'get_code' ",)"") #293
Comments
I have a similar AttributeError, on a different attribute: I have the following package versions in my virtualenv:
and jedi version |
Which function are you calling when the error occurs?
…On Oct 12, 2017 06:26, "Alberto Donato" ***@***.***> wrote:
I have a similar AttributeError, on a different attribute: (error
"\"AttributeError(\\\"'module' object has no attribute
'defined_names'\\\",)\"")
I have the following package versions in my virtualenv:
$ pip freeze
epc==0.0.5
jedi==0.11.0
jediepcserver==0.2.7
parso==0.1.0
pkg-resources==0.0.0
sexpdata==0.0.3
and jedi version 20160425.2156
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#293 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ALS35kfLegyNQj3FQmfHVvqfjx6A6tHAks5srgWIgaJpZM4Pmtd9>
.
|
@sdilts I'm not calling anything explicitly, this keeps popping up in messages when I edit python files, even if I just open an empty one. |
This is a trace of the server running with debug:
|
My eldoc-style call signature help recently stopped working. If I run
|
It seems |
@albertodonato I uninstalled jedi 0.11.0 in my emacs' virtualenv and installed jedi 0.10.2 and now my eldoc-style call signature help is working again 😄 |
@jrab89 the PR above fixes it for me with 0.11.0 too |
There is a second place where it needs to be changed, which I added in this pull request: Fixed Issue #294 |
Any update? |
(This message is intended for newbies like me). I tried the solution of @albertodonato and @sdilts but my level in emacs and python was too low to make it work (I modified by hand line 103 105 and 179 of jediepcserver.py of the folder elpa/jedi-core/ + installing again everything). The solution of @jrab89 was the winner: i installed in my real python (compared to the virtualenv one created by jedi.el) an older version of jedi: pip3 install jedi==0.10.2 (pip3 because I run python on mac OS which is a mess: https://docs.brew.sh/Homebrew-and-Python.html) By the way, yes, jedi and jedi.el are two completely different "things". Then an old-fashioned copy and replace of the two folders jedi/ jedi-0.10.2.dist-info/ located in the site-packages/ folder of my real python3 environment in the site-packages/ folder of the virtualenv created by jedi.el did the trick. Good luck! |
Hi , I've taken over maintainership of emacs-jedi and hopefully now we will be able to catch up with the recent jedi developments. I believe I have fixed this issue with #315. Please, try out the current master branch and let me know if it persists. |
This error occurs whenever a functions signature is grabbed with
jedi:get-in-function-call
, and originates at line 103:emacs-jedi/jediepcserver.py
Line 103 in b0764f4
This prevents jedi-mode from doing any sort of function signature completion.
Package version is
20160425.2156
. The relevant code in my.emacs
file isI have uninstalled/reinstalled
jedi-mode
through the package manager several times, as well removing the server manually deleting the installation folder. The server has then always been reinstalled withjedi:install-server
.The text was updated successfully, but these errors were encountered: