Undefined environment variables are redefined in build script environment for multi-output builds #5323
Closed
2 tasks done
Labels
type::bug
describes erroneous operation, use severity::* to classify the type
Checklist
What happened?
"Use Environment Variables" in the
conda-build
docs says the following about variables inbuild.script_env
in recipes (my emphasis)(link)
As of #5105,
conda-build
does not behave that way for multi-output recipes. As of that PR, any variable mentioned in the recipe'sbuild.script_env
but not found in the environment whereconda-build
is called from will be set to the empty string''
in the build script environment.For example, with a recipe like this:
I'd expect that build script to fail if run in an environment without environment variable
SPARKLY_UNICORN
set.Instead, it succeeds, because environment variable
SPARKLY_UNICORN
is defined and set to the empty string''
in the build script environment.Conda Info
Conda Config
Conda list
Additional Context
I believe this is a behavior change that was introduced recently, in #5105.
The text was updated successfully, but these errors were encountered: