diff options
| author | Harmen Stoppels <harmenstoppels@gmail.com> | 2021-10-05 20:25:43 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-10-05 18:25:43 +0000 |
| commit | d998ea1bd41b4cf7f47caa734b7c7df86178ef0c (patch) | |
| tree | 3fff7e0cd84f77890b28a191edce292a29673749 /README.md | |
| parent | 713bbdbe7c1c2078abdc09bf515b3f934e87d741 (diff) | |
| download | spack-d998ea1bd41b4cf7f47caa734b7c7df86178ef0c.tar.gz spack-d998ea1bd41b4cf7f47caa734b7c7df86178ef0c.tar.bz2 spack-d998ea1bd41b4cf7f47caa734b7c7df86178ef0c.tar.xz spack-d998ea1bd41b4cf7f47caa734b7c7df86178ef0c.zip | |
Move shell aware env into spack.environment.shell (#25608)
Cherry-picked from #25564 so this is standalone.
With this PR we can activate an environment in Spack itself, without computing changes to environment variables only necessary for "shell aware" env activation.
1. Activating an environment:
```python
spack.environment.activate(Environment(xyz)) -> None
```
this basically just sets `_active_environment` and modifies some config scopes.
2. Activating an environment **and** getting environment variable modifications for the shell:
```python
spack.environment.shell.activate(Environment(xyz)) -> EnvironmentModifications
```
This should make it easier/faster to do unit tests and scripting with spack, without the cli interface.
Diffstat (limited to 'README.md')
0 files changed, 0 insertions, 0 deletions