| Name |
Last commit
|
Last Update |
|---|---|---|
| .. | ||
| operations | ||
| __init__.py | ||
| authenticator.py | ||
| base_installer.py | ||
| chef.py | ||
| chooser.py | ||
| executor.py | ||
| installer.py | ||
| noop_installer.py | ||
| pip_installer.py |
This ensures to use the correct python executable. Using `run` simply uses `sys.prefix` with a bin suffix, which is not necessarily the currently used python executable. E.g. when linking a specific python version to a custom directory, using `sys.prefix` may point to the wrong python version: * /usr/bin/python2.7 * /usr/bin/python3.6 * /usr/bin/python is a symlink to 2.7 * /usr/bin/local/python (or any other location) is a symlink to 3.6 which shadows the former symlink `sys.prefix` is `/usr` in this case, which is correct, but the `python` executable there points to the wrong version. `run_pip` in the env fixes this already by using `sys.executable`, see https://github.com/python-poetry/poetry/blob/develop/poetry/utils/env.py#L964 This should be used in the executor as well. Co-authored-by: Jonathan Striebel <jstriebel@users.noreply.github.com>
| Name |
Last commit
|
Last Update |
|---|---|---|
| .. | ||
| operations | Loading commit data... | |
| __init__.py | Loading commit data... | |
| authenticator.py | Loading commit data... | |
| base_installer.py | Loading commit data... | |
| chef.py | Loading commit data... | |
| chooser.py | Loading commit data... | |
| executor.py | Loading commit data... | |
| installer.py | Loading commit data... | |
| noop_installer.py | Loading commit data... | |
| pip_installer.py | Loading commit data... |