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

Use python specified as runtime in the virtualenv #156

Merged
merged 2 commits into from
Apr 26, 2018

Conversation

azatoth
Copy link
Contributor

@azatoth azatoth commented Apr 25, 2018

A issue has been that even if you specify python3.6 as runtime in lambda.json, it will use python2 for the virtualenv and thus install possibly incompatible libraries (psycopg2-binary for example)
Closes: #142
Relates: #152

@azatoth azatoth force-pushed the py3venv branch 2 times, most recently from 5c30b4b to 1a1554a Compare April 25, 2018 07:29
A issue has been that even if you specify python3.6 as runtime in lambda.json,
it will use python2 for the virtualenv and thus install possibly incompatible
libraries (psycopg2-binary for example)

This changes the behavour to use the defined "runtime" in lambda.json as
basis for the virtualenv.

Closes: rackerlabs#142
Relates: rackerlabs#152
@jarosser06
Copy link
Contributor

Looks good thanks for the PR.

@jarosser06 jarosser06 merged commit a30c7bb into rackerlabs:master Apr 26, 2018
@azatoth azatoth deleted the py3venv branch April 26, 2018 19:04
@azatoth
Copy link
Contributor Author

azatoth commented Apr 27, 2018

@jarosser06 going to make a new release for this one?

@jarosser06
Copy link
Contributor

Yes. I’ll try and get it done today.

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

Successfully merging this pull request may close these issues.

2 participants