You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 8, 2022. It is now read-only.
For needls installation we need to know the python env quite early.
This is problematic in VS-Code, as it self references different python locations:
During startup: It's often the system-wide installed
Then during loading of the Python Extension, is may be the just found .venv.
After loading it may be a hard-coded / configured venv by the user.
So there is a high risk, that needls gets installed in the wrong venv is later not available.
Solution
Provide a setting, which asks for the correct Python path.
If not set, it shall be detected automatically and set as values.
If the value is set, then Open-Needs IDE is always using this value.
It shall support {$workspacefolder}.
The text was updated successfully, but these errors were encountered:
For needls installation we need to know the python env quite early.
This is problematic in VS-Code, as it self references different python locations:
.venv
.So there is a high risk, that needls gets installed in the wrong venv is later not available.
Solution
Provide a setting, which asks for the correct Python path.
If not set, it shall be detected automatically and set as values.
If the value is set, then Open-Needs IDE is always using this value.
It shall support
{$workspacefolder}
.The text was updated successfully, but these errors were encountered: