Skip to content
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

-n does not auto-accept prompts for poetry cache clear #6572

Closed
4 tasks done
novafacing opened this issue Sep 20, 2022 · 2 comments
Closed
4 tasks done

-n does not auto-accept prompts for poetry cache clear #6572

novafacing opened this issue Sep 20, 2022 · 2 comments
Labels
kind/bug Something isn't working as expected status/triage This issue needs to be triaged

Comments

@novafacing
Copy link

novafacing commented Sep 20, 2022

  • Poetry version: 1.2.1
  • Python version: 3.8
  • OS version and name: Fedora Linux Rawhide
  • pyproject.toml: Not relevant for this issue.
  • 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

Pretty simple issue, the --no-interaction flag does not actually ensure no interaction for
poetry cache clear --all PyPI for example, it just fails because it didn't get the yes
response to the prompt.

What I'd like to see is either:

  • -n implicitly respond yes to this prompt or
  • -y option added to explicitly respond yes to this prompt

I don't have time to add it myself right this second, but I may get to it myself if this is a feature others agree with.

@novafacing novafacing added kind/bug Something isn't working as expected status/triage This issue needs to be triaged labels Sep 20, 2022
@dimbleby
Copy link
Contributor

duplicate #6291

Copy link

github-actions bot commented Mar 1, 2024

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Something isn't working as expected status/triage This issue needs to be triaged
Projects
None yet
Development

No branches or pull requests

2 participants