You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried the fix proposed in #4047, but it did not fully resolve the issue. It populates the environment variable in the shell; however, it doesn't make the environment variable available in the command section itself. That is, it made the environment variable accessible via $(env), but referencing it with ${MY_ENV_VAR} yields no results.
Prerequisites
pip check
does not report any conflictsEnvironment
What happened
The
env
option of the shell dependency has no effect, despite what the documentation claims.I suspect this has been broken since #3958
I tried the fix proposed in #4047, but it did not fully resolve the issue. It populates the environment variable in the shell; however, it doesn't make the environment variable available in the command section itself. That is, it made the environment variable accessible via
$(env)
, but referencing it with${MY_ENV_VAR}
yields no results.Reproducing example
The text was updated successfully, but these errors were encountered: