-
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 1.7.0 poetry init
fails with "Poetry could not find a pyproject.toml ..."
#8634
Comments
poetry init
fails with poetry init
fails with "Poetry could not find a pyproject.toml ..."
poetry init
fails with "Poetry could not find a pyproject.toml ..."poetry init
fails with "Poetry could not find a pyproject.toml ..."
Confirming, interactive dependencies are busted when creating a new project. |
Am also running into this - I guess the solution is to pin 1.6.1 for now |
Hey, thanks for reporting. This one is a bit strange. I can reproduce it within a docker container, but not on my "normal" system. Also a
@Secrus any chance this has something to do with cleo? fin swimmer |
I think it's a regression from #8559, which now tries to get hold of the poetry configuration before the poetry object exists. (untested theory, but it sounds plausible) |
@duncanariey alternatively if you |
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. |
Poetry version: Poetry (version 1.7.0)
Python version: Python 3.11.6 (main, Nov 1 2023, 10:08:51) [GCC 12.2.0]
OS version and name: Debian 12, macOS 14.1
pyproject.toml: N/A, file was never created by
poetry init
I am on the latest stable Poetry version, installed using a recommended method.
I have searched the issues of this repo and believe that this is not a duplicate.
I have consulted the FAQ and blog for any relevant entries or release notes.
If an exception occurs when executing a command, I executed it again in debug mode (
-vvv
option) and have included the output below.Issue
Running
poetry init
with poetry 1.7.0 and then interactively adding dependencies causes an error. The error is not seen if you skip adding dependencies.This same thing does not fail with poetry 1.6.1:
The text was updated successfully, but these errors were encountered: