-
Notifications
You must be signed in to change notification settings - Fork 293
Python not picked up on path #100
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
Comments
Yeah, that should work out of the box. My only guess is that your |
Oh wait.. i see the |
Removed all pieces that didn't seem to affect the minimal example: ---
service:
name: foo
frameworkVersion: ">=1.24.0" # Only version tested
plugins:
- serverless-python-requirements
# custom:
# pythonRequirements:
# pythonBin: python
provider:
name: aws
functions:
dispatch:
handler: dispatch.handler
runtime: python3.6 The required python is first on path, but above example only works if I uncomment the |
This line is looking for The Serverless docs allow for an optional override in the function directive. This may be a misunderstanding on my part, but I assumed I can specify the runtime at function level without setting a provider-level default (given my full example runs one method in node and one in python, setting a default didn't make much sense to me). |
Ah, yes, this plugin doesn't support per function packaging, so it uses the global provider specification, you'll have to set it for the plugin to work. |
I could default it to |
(these refer to the same python 3.6 installation). The pyenv shim is on path, yet the serverless plugin fails to pick it up:
I can fix this with the following directive:
but isn't this just referencing the same Python it should be using by default? Should this not work out of the box?
The text was updated successfully, but these errors were encountered: