There could be several reasons why the installed editable packages are not being detected by pylsp:
The editable package may not have been installed in the correct location. Ensure that the package is installed in the appropriate site-packages directory where Python can discover it.
The package may not have a valid metadata file. Check that the package contains a valid setup.py file with the required metadata and that it has been installed correctly.
The pylsp server may not have been configured to look for editable packages. Check the configuration settings for the pylsp server and ensure that it is configured to detect editable packages.
There may be a conflict with other installed packages. Check that there are no conflicting dependencies or versions of other packages that could be causing issues.
Restarting the IDE or the pylsp server might be necessary. Sometimes, a simple restart can solve the issue.
If none of the above solutions work, there may be a deeper issue that requires more investigation.
Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss
Asked: 2023-06-21 12:12:16 +0000
Seen: 10 times
Last updated: Jun 21 '23
How can I use oversampling to address a problem?
What is the process for obtaining metadata from my Python-Django project in order to execute SSO?
How can Django Admin accommodate a variety of formats and locales for its input fields?
How can an array be passed using typo3 flexform xml and itemsProcConfig?
Is it possible to invoke an asynchronous function without using the await keyword?