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.

Sign up for GitHub

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

Jump to bottom

Python 3.6 support #24

Closed
polendri opened this issue Apr 22, 2017 · 2 comments · Fixed by #26
Closed

Python 3.6 support #24

polendri opened this issue Apr 22, 2017 · 2 comments · Fixed by #26

Comments

@polendri
Copy link

AWS Lambda now has a Python 3.6 runtime. I tried switching my runtime to python3.6 but my functions are failing due to packaging-related errors (module initialization error: psycopg2 must be installed.), so I'd imagine some action needs to be taken here to support this.

I took a look at the source and it looks like pip is being invoked from the path, so I tried activating a venv with python3 -m venv venv; venv/bin/activate and then invoking sls deploy, but I got the same result. I'm not sure that the pip version used matters, when it's going to a specified path anyway, but perhaps it does?
@dschep
Copy link
Contributor

dschep commented Apr 23, 2017

I'll take a look. It's just a matter of calling pip3. Tho I don't think psycopg works on lambda because there's no libpq on those boxes 😕

@bsamuel-ui bsamuel-ui mentioned this issue May 2, 2017
Merged
@dschep dschep closed this as completed in #26 May 2, 2017
@polendri
Copy link
Author

polendri commented May 2, 2017

Thanks for tackling this, much appreciated!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add support for Python3.6 on AWS.
2 participants
@dschep @polendri