Further improve micromamba search output#2823
Conversation
|
@jonashaag please have a look 👀 |
|
Great, thanks! I wonder if we should have a way to enable verbose search output without the "technical" output from Mamba that typically comes with |
|
Would you envision something like |
|
Looks like the CI fails because the workflow was cancelled?
|
|
All checks are passing now. @jonashaag how should we proceed with this? |
|
I'm still not sure about the -v flag |
WDYT, should I implement this instead? |
|
@AntoinePrv @pavelzw @JohanMabille any input here? |
AntoinePrv
left a comment
There was a problem hiding this comment.
I know it is not the point of this PR, but if you can find the time to split print_solvable into a few functions while the logic is still warm in your head, it would make it more readable.
Maybe also take everything that has side effects (e.g. out) as a parameter.
For -v vs --pretty-verbose, I see no good option, the former prints too much information, while the later seems duplicate. Maybe --full?
But this is good for me anyhow., thanks for the PR!
Done in 3c737ca
Since this seems to be more of a corner case (and is probably most used for automated parsing where additional logging doesn't "distract" the user), I think I would avoid overloading the CLI with an additional parameter. So I'm fine with leaving this at |
|
Thanks for the PR! I would be in favor to keep |
Motivation
Minor fixes and changes to aesthetics in the current
micromamba searchoutput.Changes
─-vto show all builds as requested in micromamba search does not print every package #2847Examples
Single package view
Single package view
Single package verbose view with all builds
Single package verbose view with all builds (
-v)