Skip to content

Still does not work with poetry 1.0.0b1 #409

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
elendirx opened this issue Sep 21, 2019 · 6 comments
Closed

Still does not work with poetry 1.0.0b1 #409

elendirx opened this issue Sep 21, 2019 · 6 comments

Comments

@elendirx
Copy link

elendirx commented Sep 21, 2019

Poetry 1.0.0b1 changed the behaviour of export.
This was fixed according to: #395

Except it wasn't.
The requirements.txt file is not saved in case there is no editable flag.

@gusostow
Copy link

Seconded

@billyshambrook
Copy link

Is there any movement on this?

Our current hack/workaround is to have the following in the serverless.yaml

plugins:
- serverless-python-requirements
- serverless-scriptable-plugin

custom:
  pythonRequirements:
    usePoetry: false
  scriptHooks:
    before:package:createDeploymentArtifacts: poetry export --without-hashes -f requirements.txt -o requirements.txt

This works so far, but does look messy in my yaml :(

Let me know if I can help!

@jimpudar
Copy link

Also hitting this issue

@BastienM
Copy link

Bumping this issue.
Just had the same problem.

@Zepp10x
Copy link

Zepp10x commented Feb 4, 2020

Same for me, please deploy the fix to the NPM registry asap to make the plugin less frustrating to work with for new users

@bsamuel-ui
Copy link
Contributor

I'm closing this as resolved by #446

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 a pull request may close this issue.

7 participants