-
Notifications
You must be signed in to change notification settings - Fork 16
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
emacs-lsp-booster doesn't work well with emacs-pet/pyvenv regarding python virtual environment #37
Comments
Thanks for the very detailed report. Going though your log, I think the different may come from this:
vs
This client notification sends the virtual env path to the server. If this step goes wrong, it may explain what you experienced. According to the log, when I don't think the |
No,
|
Thanks for your comment, I've CCed this issue to the author of pet, @jdtsmith would you like to share your workflow with |
In the end you just need to set |
When an empty hash table is sent in What do you see from How exactly do you enable |
Not special, magical step to enable
(use-package eglot-booster
:after eglot
:config (eglot-booster-mode))
|
Hi, Thanks so much for this awsome project, it works well with all language servers along with
eglot
, except for python project with virtual environment in my case.I used to manage my virual environment with
https://github.com/jorgenschaefer/pyvenv
, then switch topet
later.But I've been struggled with
eglot-booster-mode
for a while, after I enableeglot-booster-mode
withpet
,eglot
fails to recognize all dependencies installed in the virtual environment.How to reproduce
pyright-language-server
is installed and in your PATHpython3 -m venv .venv source .venv/bin/activate pip install python-dotenv
init.el
Open the
poc.py
with(eglot-booster-mode)
enabled, flymake couldn't resolve thedotenv
packageReopen the
poc.py
with(eglot-booster-mode)
disabled, restarteglot
or restart emacs, flymake manages to resolve thedotenv
Logs
eglot-booster-mode
enabled:eglot-booster-mode
disabled:The text was updated successfully, but these errors were encountered: