diff options
| author | Massimiliano Culpo <massimiliano.culpo@gmail.com> | 2020-01-25 01:49:45 +0100 |
|---|---|---|
| committer | Todd Gamblin <tgamblin@llnl.gov> | 2020-01-24 16:49:45 -0800 |
| commit | 4d7d65736687cb03ac3c9b6ca685dca86935227a (patch) | |
| tree | 81adbfb32b9d6de1054440159969c19aae9622ba /COPYRIGHT | |
| parent | d646c8d8d5bf4cf5ddcb4ac04ce29efa5a8cd2df (diff) | |
| download | spack-4d7d65736687cb03ac3c9b6ca685dca86935227a.tar.gz spack-4d7d65736687cb03ac3c9b6ca685dca86935227a.tar.bz2 spack-4d7d65736687cb03ac3c9b6ca685dca86935227a.tar.xz spack-4d7d65736687cb03ac3c9b6ca685dca86935227a.zip | |
bugfix: make `_source_single_file` work in venvs (#14569)
Using `sys.executable` to run Python in a sub-shell doesn't always work in a virtual environment as the `sys.executable` Python is not necessarily compatible with any loaded spack/other virtual environment.
- revert use of sys.executable to print out subshell environment (#14496)
- try instead to use an available python, then if there *is not* one, use `sys.executable`
- this addresses RHEL8 (where there is no `python` and `PYTHONHOME` issue in a simpler way
Diffstat (limited to 'COPYRIGHT')
0 files changed, 0 insertions, 0 deletions