-
Notifications
You must be signed in to change notification settings - Fork 293
Deploying local file-backed distributions with pipenv fails #314
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
This seems to work if I manually perform the install from the directory where the pipfile is packaged in: cd /Users/ahonnecke/Code/repos/timescale-monitor-lambda/timescale-monitor-lambda
|
I have a pull request to fix this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a Bug Report
History
Reopening in this repo, original PR here:
serverless/serverless#5768
Description
pipenv allows users to install a local path into the pipenv created venv:
pipenv install -e './subs/panic'
Which results in an entry in the pipfile that points to the local directory:
And (while in the venv) allows the user to import the install package
However, serverless fails while attempting to deploy a service to aws lambda that contains a locally installed package as detailed above:
What went wrong?
sls deploy failed because (seemingly) pip or pipenv failed to find "./subs/panic" as a local path
What did you expect should have happened?
The project should have built in the container and deployed up to aws with dad.panic in the python namespace, specifically I expect that any packages that I can import and use by activating the virtual environment locally will:
Similar issues (possibly):
Additional Data
Serverless Framework Version you're using:
1.35.1
Operating System:
OSX 10.13.4
Stack Trace:
Provider Error messages:
Generated requirements.txt:
The text was updated successfully, but these errors were encountered: