Skip to content

fileName override fails if pyproject.toml exists #411

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

Closed
daishi opened this issue Sep 23, 2019 · 4 comments
Closed

fileName override fails if pyproject.toml exists #411

daishi opened this issue Sep 23, 2019 · 4 comments
Labels

Comments

@daishi
Copy link

daishi commented Sep 23, 2019

Situation

What happens

You end up with an error like

  Error: ENOENT: no such file or directory, open '.../.serverless/requirements.txt'
      at Object.fs.openSync (fs.js:646:18)
      at Object.fs.readFileSync (fs.js:551:33)
      at filterRequirementsFile (/home/daishi/src/p4p_backend/node_modules/serverless-python-requirements/lib/pip.js:355:6)
      at generateRequirementsFile (/home/daishi/src/p4p_backend/node_modules/serverless-python-requirements/lib/pip.js:67:5)
...

Diagnosis

Tracing execution to https://github.com/UnitedIncome/serverless-python-requirements/blob/master/lib/pip.js#L65 shows that unless you explicitly set usePoetry: false, all of the sls commands will fail with the above error.

@zygopleural
Copy link

Also seeing this error

@aspin
Copy link

aspin commented Dec 9, 2019

+1, but this happens even when I don't customize the requirements file name

@levakin

This comment has been minimized.

@bsamuel-ui bsamuel-ui added the bug label Feb 19, 2020
@bsamuel-ui
Copy link
Contributor

Duplicate of #400 .

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

No branches or pull requests

5 participants