Skip to content
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

Open
Miserlou opened this issue Mar 29, 2016 · 2 comments
Open

Non-Namespace Packages Don't Work on AWS Lambda #45

Miserlou opened this issue Mar 29, 2016 · 2 comments

Comments

@Miserlou
Copy link
Owner

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"

@jamescooke
Copy link

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 /tmp and run the target script...

ImportError: No module named apputils

I can see that this work around has placed the __init__.py file in the google folder, but that doesn't solve the problem. I'd already tried this solution when manually building the zip file before I found zappa and had given up on it.

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.

@Miserlou
Copy link
Owner Author

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants