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

Get more consistent output from poetry show #9597

Open
ch1nq opened this issue Aug 1, 2024 · 1 comment · May be fixed by #9580
Open

Get more consistent output from poetry show #9597

ch1nq opened this issue Aug 1, 2024 · 1 comment · May be fixed by #9580
Labels
kind/feature Feature requests/implementations status/triage This issue needs to be triaged

Comments

@ch1nq
Copy link

ch1nq commented Aug 1, 2024

Issue Kind

Change in current behaviour

Description

Currently, the output of poetry show depends on the width of the terminal of the caller. This means that some information might get truncated if the terminal is not wide enough. While this makes for a more more readable output for the user, it becomes less ideal when calling the command from a script, where the notion of terminal width does not make sense.

In order to get a more consistent output from the poetry show command, there should be a --no-truncate flag added to the command. When the flag is set, the show command does not take the width of the terminal into account when deciding the level of detail to print.

Impact

If poetry show is called from a script that processes the output downstream, it needs the command to give a consistent output.

Workarounds

Currently, it is possible to set an arbitrarily large fake terminal width, in order to achieve to ensure nothing is truncated. E.g., setting environment variable COLUMNS={large number}. However, this is very much a hack and does not seem like the right solution.

@ch1nq ch1nq added kind/feature Feature requests/implementations status/triage This issue needs to be triaged labels Aug 1, 2024
@ch1nq ch1nq linked a pull request Aug 1, 2024 that will close this issue
2 tasks
@dimbleby
Copy link
Contributor

dimbleby commented Aug 1, 2024

there is no need to have an issue and a pull request, just the pull request is sufficient

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Feature requests/implementations status/triage This issue needs to be triaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants