reduce message width

[nsheff]

It would be nice if the logmuse options were very compact so they didn't clutter the help CLI output of a tool that uses logmuse. look at this:

version: 0.4.0-dev
usage: refgenie [-h] [-V] [-c GENOME_CONFIG] [--logdev]
                [--verbosity VERBOSITY] [--silent]
                {pull,build,list,init,listr} ...

refgenie - builds and manages reference genome assemblies

positional arguments:
  {pull,build,list,init,listr}
    pull                Download assets.
    build               Build genome assets
    list                List available local genomes.
    init                Initialize a genome configuration.
    listr               List available genomes and assets on server.

optional arguments:
  -h, --help            show this help message and exit
  -V, --version         show program's version number and exit
  -c GENOME_CONFIG, --genome-config GENOME_CONFIG
  --logdev              Expand content of logging message format.
  --verbosity VERBOSITY
                        Set logging level (integer from 0-5 or Python builtin)
  --silent              Silence logging. Overrides --verbosity.

In this PR I chagned the logdev and verbosity help messages to fit on one line, which is nice. However, because "VERBOSITY" is so long, it still takes up 2 lines regardless of size of the help message. See this question for a complete description of what I mean.

I propose: we change the dest for verbosity to be shorter... just V perhaps? that will solve this problem without requiring every tool that uses logmuse to have a custom help formatter.

[vreuter]

It would be nice if the logmuse options were very compact so they didn't clutter the help CLI output of a tool that uses logmuse.
...
I propose: we change the dest for verbosity to be shorter... just V perhaps? that will solve this problem without requiring every tool that uses logmuse to have a custom help formatter.

Yep, sounds good to me. Here are the places I see locally that we're using logmuse and that may need to change, if the CLI namespace is accessing a verbosity attribute:

~/code/geofetch/requirements/requirements-all.txt:4:logmuse>=0.0.2
~/code/refgenie/requirements/requirements-all.txt:2:logmuse>=0.1
~/code/looper/requirements/requirements-all.txt:3:logmuse>=0.0.2
~/code/caravel/caravel/requirements/requirements-all.txt:6:logmuse
~/code/peppy/requirements/requirements-all.txt:5:logmuse>=0.0.2
~/code/lucidoc/requirements/requirements-all.txt:1:logmuse>=0.0.2
~/code/refgenieserver/requirements/requirements-all.txt:4:logmuse

Do you know any others?

[nsheff]

much better, thanks.

[nsheff]

just crossed my mind -- would it be possible to just name it "V" in the help, but then duplicate that over to verbosity after the fact? not sure if that's better than changing everything depending on this...

[vreuter]

@nsheff tail of refgenie --help now looks like this for me:

optional arguments:
  -h, --help            show this help message and exit
  -V, --version         show program's version number and exit
  -c GENOME_CONFIG, --genome-config GENOME_CONFIG
  --logdev              Expand content of logging message format.
  --silent              Silence logging. Overrides --verbosity.
  --verbosity V         Set logging level (integer from 0-5 or Python builtin)

https://refgenie.databio.org

I think this will spare us needing to change all the dependents.

[nsheff]

awesome, I forgot about metavar and its difference with dest... this is exactly what we want! sweet.

[nsheff]

🏆 !