-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
'poetry init' should use existing pyproject.toml file #1639
Comments
Hello @dekoza , sounds like a good idea to me 👍 I would really like to see your PR :) fin swimmer |
I would like to see this feature too! It would be very helpful when paired with Cookiecutter templates. |
I'm sorry, my commercial project really eats up a lot of my time lately. If anyone wants to take over, don't hesitate 🙂 |
At the moment a `poetry init` will fail, if a pyproject.toml already exists. This change ensures pyproject.toml is reused if no build-system has already been defined or poetry is not already configured. Resolves: #1639
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Feature Request
I think that
poetry init
should detect if existing pyproject.toml already contains poetry entries and if not, it should add itself to it instead of exiting with error. I have basic (almost brute-force) method prepared but I want to make it in more elegant way. Anyway, expect PR soon 😄The text was updated successfully, but these errors were encountered: