diff options
| author | Massimiliano Culpo <massimiliano.culpo@gmail.com> | 2020-01-25 01:49:45 +0100 |
|---|---|---|
| committer | Todd Gamblin <tgamblin@llnl.gov> | 2020-02-07 16:36:23 -0600 |
| commit | 010f9451c9d27fb1e8b73802876123573c872d17 (patch) | |
| tree | d0944c26d5de49e1702d4ae2dbc25fe25bc400fe /NOTICE | |
| parent | f9f28e8fbaaf6bbc3fa72050bfce34d6fad25173 (diff) | |
| download | spack-010f9451c9d27fb1e8b73802876123573c872d17.tar.gz spack-010f9451c9d27fb1e8b73802876123573c872d17.tar.bz2 spack-010f9451c9d27fb1e8b73802876123573c872d17.tar.xz spack-010f9451c9d27fb1e8b73802876123573c872d17.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 'NOTICE')
0 files changed, 0 insertions, 0 deletions