summaryrefslogtreecommitdiff
path: root/.flake8
diff options
context:
space:
mode:
authorHarmen Stoppels <harmenstoppels@gmail.com>2021-10-15 10:00:44 +0200
committerGitHub <noreply@github.com>2021-10-15 10:00:44 +0200
commite0fbf09239fb25760e07cc984f544ddb98e61f22 (patch)
treed96ddbce38beda8ad8f524d8ff7693b7347246af /.flake8
parent842e56efb87dce66f50504a9a01e87d996dcac50 (diff)
downloadspack-e0fbf09239fb25760e07cc984f544ddb98e61f22.tar.gz
spack-e0fbf09239fb25760e07cc984f544ddb98e61f22.tar.bz2
spack-e0fbf09239fb25760e07cc984f544ddb98e61f22.tar.xz
spack-e0fbf09239fb25760e07cc984f544ddb98e61f22.zip
EnvironmentModifications: allow disabling stack tracing (#26706)
Currently Spack keeps track of the origin in the code of any modification to the environment variables. This is very slow and enabled unconditionally even in code paths where the origin of the modification is never queried. The only place where we inspect the origins of environment modifications is before we start a build, If there's an override of the type `e.set(...)` after incremental changes like `e.append_path(..)`, which is a "suspicious" change. This is very rare though. If an override like this ever happens, it might mean a package is broken. If that leads to build errors, we can just ask the user to run `spack -d install ...` and check the warnings issued by Spack to find the origins of the problem.
Diffstat (limited to '.flake8')
0 files changed, 0 insertions, 0 deletions