Skip to content

Pipenv local editable packages won't deploy #476

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

Open
thejuan opened this issue Feb 25, 2020 · 3 comments
Open

Pipenv local editable packages won't deploy #476

thejuan opened this issue Feb 25, 2020 · 3 comments

Comments

@thejuan
Copy link

thejuan commented Feb 25, 2020

I'm using a pipfile with a section like this

[packages.common]
editable = true
path = "./../common"

Gives the error

STDERR: ERROR: Invalid requirement: './../common' (from line 1 of /var/task/requirements.txt)
Hint: It looks like a path. File './../common' does not exist.

#314 seems to be similar, the only difference is my package is a sibling folder

@miketheman
Copy link
Contributor

@thejuan thanks for the report! Would you mind providing the version of serverless, the plugins, pipenv, Python? Also, the generated requirements.txt file from pipenv lock -r

@thejuan
Copy link
Author

thejuan commented Feb 26, 2020

pipenv, version 11.9.0
python 3.7.5
serverless
Framework Core: 1.64.0
Plugin: 3.4.0
SDK: 2.3.0
Components Core: 1.1.2
Components CLI: 1.4.0

plugins

  - serverless-jetpack
  - serverless-scriptable-plugin
  - serverless-reqvalidator-plugin
  - serverless-aws-documentation
  - serverless-offline
  - serverless-domain-manager
  - serverless-plugin-bind-deployment-id
  - serverless-plugin-warmup
  - serverless-content-encoding
  - serverless-plugin-scripts
  - serverless-plugin-split-stacks
  - serverless-dependson-plugin
  - api-gateway-stage-tag-plugin
  - serverless-plugin-package-json
  - serverless-openapi-documentation
  - serverless-plugin-additional-stacks
  - serverless-python-requirements

requirements

 -e ./../common
 boto3==1.12.6
 botocore==1.15.6

@thejuan
Copy link
Author

thejuan commented Feb 26, 2020

Workaround for now is to use nodeploy and then include the other package into the serverless package via include

noDeploy:
      - ./../common


package:
  include:
    - build/**
    - "src/**/*.py"
    - "../common/*.py"

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

No branches or pull requests

2 participants