Closed twmr closed 2 years ago
I can't help you if I can't reproduce it and you've deleted all the things I've asked for in the issue template lol
lsp-jedi-executable-command
is declared and defined buffer-locally if you just use pet-mode
as a major mode hook to python-mode
, even if jedi-language-server
can't be found.
Not sure if the path in In "../../../../.pylintrc": is determined by pet.el. If yes, it could be converted to an absolute path before it is output.
That's pylint's error output. Nothing I can do here/
Which Emacs version are you running? What's your configuration? How is your project set up? Where are your virtualenv executables located? All vital information for any actionable bug report.
I can't help you if I can't reproduce it and you've deleted all the things I've asked for in the issue template lol
Sry about that. I thought that the info that I provided in the description of the issue is sufficent. I've just update the description. Let me now if anything is still missing.
lsp-jedi-executable-command is declared and defined buffer-locally if you just use pet-mode as a major mode hook to python-mode, even if jedi-language-server can't be found.
I don't use pet-mode
but the advanced config mentioned in the readme (see description of the github issue).
That's pylint's error output. Nothing I can do here/
You are right. This error is visible even when pet
is not configured. It is output by flycheck
.
So the only remaining issue that I have is this one.
mapc: Symbol’s value as variable is void: lsp-jedi-executable-command
Did you try the latest version?
Now, I've just tested the latest version and the issue is gone now. Thx!
Description
When I run
pet-verify-setup
in e.g. the pytest git repo, the following messages are output in my Messages bufferI have a .pylintrc file in my homedir, which probably is not compatible with the pylint executable that was found by
pet-find-executable
.jedi is probably not installed anywhere, that's why I gest the symbol's value as var is void message (not 100% sure).
Expected behavior
The symbol's value as var is void message is probably an issue with pet.el, which should be fixed.
Not sure if the path in
In "../../../../.pylintrc":
is determined by pet.el. If yes, it could be converted to an absolute path before it is output.The warnings that are output in Messages should be output in the
*pet*
buffer instead similar to the way this is done inflycheck-verify-setup
.Desktop (please complete the following information):
System tools versions
Additional context
Output of
M-x (pet-verify-setup)
pet config