Open tim-schier-frontier opened 7 years ago
I spun up a Docker container running Jessie, pulled my same code, installed the virtual environment and ran zappa update dev
and it all works.
Looking in the zip file, I can see nacl/_sodium.cpython-36m-x86_64-linux-gnu.so
.
Context
I'm using paramiko which uses PyNaCl. After deploying, I get an error log that finishes with:
Looking in the zip file that was uploaded, I can see the a file
nacl/_sodium.cp36-win_amd64.pyd
, but not the Linux equivalent. If I download the manylinux wheel from PyPI, I see a file_sodium.cpython-36m-x86_64-linux-gnu.so
in there.So my question is how should I manage this - developing on a Windows machine but wanting Zappa to deploy to Lambda?
Steps to Reproduce
Set up development environment in Windows. In the virtual environment:
pip install paramiko==2.2.1
In the Flask app file:import paramiko
Runzappa deploy dev
Access the web hook url. Runzappa tail
to see the error.Note if the
import paramiko
is removed then it works fine.Your Environment
Windows 10 1703 64 bit Python 3.6.2 Zappa 0.43.1
zappa_settings.yml:
pip freeze output: