-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add settings for PYTHONPATH and python executable #11
Comments
NB: it's PYTHONPATH/pythonpath not PYTHON_PATH |
Changed param |
Added "configuration": {
"title": "Python settings for Pysys",
"properties": {
"pysys.interpreter_path": {
"type": "string",
"description": "Path to Python that has Pysys installed. This overrides the default of using python on the PATH."
},
"pysys.PYTHONPATH": {
"type": "string",
"description": "PYTHONPATH will be *Added* to the environment when running pysys."
}
} interpreter_path will now effect the python used to invoke pysys. Need to add handling for PYTHONPATH so that it will be added to the environment when the pysys command runs. |
We should also consider fitting in with what the Python VSCode plugin does e.g. use a .env file and/or venv (https://code.visualstudio.com/docs/python/environments#:~:text=In VS Code, PYTHONPATH can be set through,is routed through the terminal such as debugging) - would be good to recommend a single approach that would work for both, since they'll almost always be used together |
To help the user we should allow them to override the default python on the path with their own choice.
This should be explicitly overridden not set by default.
These settings will replace the default command used when invoking commands. Where we currently use
python -m pysys
If the python executable is set to be
/mypath/bin/python
orc:\myWindowsPath\bin\python.exe
we should use these/mypath/bin/python -m pysys ...
The text was updated successfully, but these errors were encountered: