Unsolicited messages output to stdout, --quiet does not do anything

1. Install Poetry 0.12.17
2. poetry config settings.virtualenvs.create false
3. Try to run something using poetry run. Observe that a message “Skipping virtualenv creation, as specified in config file.” is output to stdout.
4. Try poetry -q run, poetry run --quiet and other variations thereof. Observe that nothing is run and an exception is raised.

There should be a way to suppress all output other than that of the command being run. Otherwise it’s impossible to run scripts reliably.

[benriou]

I would be interested on an update on this. 😃

[sfermigier]

I’ve been struggling with a similar issue (with Poetry 1.1.4) and I believe I have found several inconsistencies:

• poetry -q install is quiet, but doesn’t do anything (seemingly)
• poetry install -q works, but is as verbose as poetry install
• poetry -q update doesn’t do anything (quietly)
• poetry update -q works as expected, quietly
• poetry --ansi <whatever> gives an error message. Same with --no-ansi or -v.

This is also inconsistent with the usage:

USAGE
  poetry [-h] [-q] [-v [<...>]] [-V] [--ansi] [--no-ansi] [-n] <command> [<arg1>] ... [<argN>]

Ideally, it shouldn’t matter wether -q, -v, --ansi, etc. are before or after the command.