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
When you use the Pipenv shell, it sets an environment variable, VIRTUAL_ENV. This is relied upon by some 3rd party packages, namely Zappa, to work properly.
But when you use pipenv run to run Zappa, it can't find the VIRTUAL_ENV variable, and ends up not working correctly.
I think that both commands should maintain the same execution environment for subcommands, including having the same set of environment variables.
This is because activate_this.py does not set VIRTUAL_ENV. I have opened a pull request on pypa/virtualenv ( pypa/virtualenv#1057 ), but no response yet.
Summary
When you use the Pipenv shell, it sets an environment variable,
VIRTUAL_ENV
. This is relied upon by some 3rd party packages, namely Zappa, to work properly.But when you use
pipenv run
to run Zappa, it can't find theVIRTUAL_ENV
variable, and ends up not working correctly.I think that both commands should maintain the same execution environment for subcommands, including having the same set of environment variables.
To Replicate
Within shell
Using the
run
commandThe text was updated successfully, but these errors were encountered: