Skip to content
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

jedi should not be imported into the active (lispy--python-proc) #678

Open
QiangF opened this issue Feb 11, 2024 · 2 comments
Open

jedi should not be imported into the active (lispy--python-proc) #678

QiangF opened this issue Feb 11, 2024 · 2 comments

Comments

@QiangF
Copy link

QiangF commented Feb 11, 2024

Like an lsp server, jedi should live outside of the working virtual environment. The ":environment" should be specified in a .dir-locals

@QiangF
Copy link
Author

QiangF commented Feb 11, 2024

So either use jedi.el or import jedi in current environment. Currently there is a mixed of the two.

@QiangF
Copy link
Author

QiangF commented Feb 11, 2024

The dependency on jedi might be better replaced with a language server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant