-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Non-Namespace Packages Don't Work on AWS Lambda #45
Comments
Sorry to jump on a closed Issue - I don't think this is fixed. It appears to me that https://github.com/google/google-apputils/ does not work with this work around. Using latest zappa to build a zip, when I grab that zip, unpack it into
I can see that this work around has placed the Unfortunately, I've experimented with various solutions to for this Google package for a number of hours and still haven't found a work around. |
Hm. Google are doing something funky with their packaging. If you can find a way to fix this, let me know or send a PR and we can add it in! |
Miserlou#45. fixes Pyramid support.
I think we just need to throw init.py in there if there isn't one.
"hey, fun fact. python namespace packages don't work by default in AWS Lambda
so far, that means all zope._, repoze._, and google.* packages don't work by copying them out of a virtualenv"
The text was updated successfully, but these errors were encountered: