Open jneves opened 3 years ago
This seems to be true of all commands: zappa update dev --no_venv
also fails with the same error on my (brand-new ubuntu VM) build.
Hi there! Unfortunately, this Issue has not seen any activity for at least 90 days. If the Issue is still relevant to the latest version of Zappa, please comment within the next 10 days if you wish to keep it open. Otherwise, it will be automatically closed.
I can confirm that this is still an issue.
Originally from: https://github.com/Miserlou/Zappa/issues/2097 by woodrad
Context
Running
zappa package production --no_venv
throwsTypeError: expected str, bytes or os.PathLike object, not NoneType
. This error happens only when running outside of a virtual environment.zappa package production
works as expected.While I believe running
zappa
outside of a virtual environment using--no_venv
is supported (per #835), I understand why this would be a low-priority issue.Expected Behavior
zappa
builds an application package.Actual Behavior
zappa
throws the following error:Possible Fix
If running
zappa package
outside of a virtual environment is not supported, then the resolution to this issue would be removing support forzappa package --no_venv
or reverting #1891.Another option is adding a conditional check to
splitpath()
to see whether we are running in a virtual environment before runningsplitpath(venv)
.What appetite do the project maintainers have for supporting
zappa
use outside of virtual environments?Your Environment
3.8-alpine3.11
Docker image)pip freeze
:zappa_settings.json
: the error can be reproduced no matter what's inzappa_settings.json