-
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 - Pressing <enter> at "Enter package # to add ..." causes AttributeError: 'NoneType' object has no attribute 'replace' #2355
Comments
Additional occurrence of the issue, with a stack trace (via
Python 3.9.0 + Poetry 1.1.8 on macOS. Pretty sure this just needs a default value of |
Fixes python-poetry#2355 This works around an issue with cleo's `Command.choice` implementation. If the user does not make a selection then an AttributeError is raised.
Fixes python-poetry#2355 This works around an issue with cleo's `Command.choice` implementation. If the user does not make a selection then an AttributeError is raised.
I think this issues comes from cleo's ChoiceQuestion not supporting an empty choice. IMO, it makes sense to update |
Otherwise, an AttributeError is raised. See related downstream ticket: python-poetry/poetry#2355 Signed-off-by: Jacob Perron <[email protected]>
I've also opened a related patch upstream: python-poetry/cleo#109 |
Fixes python-poetry#2355 This works around an issue with cleo's `Command.choice` implementation. If the user does not make a selection then an AttributeError is raised.
Fixes #2355 This works around an issue with cleo's `Command.choice` implementation. If the user does not make a selection then an AttributeError is raised.
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. |
-vvv
option). (it made no difference in the output)Issue
very minor, but I expect a human-readable error message instead, or to default to the first one (it was an exact name match after all!)
The text was updated successfully, but these errors were encountered: