pipenv install --quiet is noisy

[jgillich]

Issue description

$ pipenv --quiet install
Installing dependencies from Pipfile.lock (d60503)...
  🐍   ▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉ 0/0 — 00:00:00
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.

Expected result

No logging

Actual result

See above

[matteius]

@jgillich there is no longer the progress bar in pipenv, and the current example looks like:

matte@LAPTOP-N5VSGIBD MINGW64 ~/Projects/pipenv (main)
$ pipenv install --quiet --dev
Loading .env environment variables...
Installing dependencies from Pipfile.lock (ccf32d)...

Are you looking for no logging at all or is this acceptable?

[larsch]

No amount of --bare or --quiet stops pipenv from printing a lot of information that is mostly useless to the average user.

I find pipenv excessively noisy for every day use and automated environments.

% pipenv --quiet --bare install --quiet

Creating a virtualenv for this project...
Pipfile: C:\Work\Test\Pipfile
Using C:/Program Files/Python310/python.exe (3.10.11) to create virtualenv...
[  ==] Creating virtual environment...created virtual environment CPython3.10.11.final.0-64 in 343ms
  creator CPython3Windows(dest=C:\Users\User\.virtualenvs\Test-LmV5Su2d, clear=False, no_vcs_ignore=False, global=False)
  seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=C:\Users\User\AppData\Local\pypa\virtualenv)
    added seed packages: pip==23.1.2, setuptools==67.7.2, wheel==0.40.0
  activators BashActivator,BatchActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator

Successfully created virtual environment!
Virtualenv location: C:\Users\User\.virtualenvs\Test-LmV5Su2d
Installing dependencies from Pipfile.lock (5246b3)...
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.

[spt29]

I second that request: When one specifies --quiet, one expects a tools to follow The Rule of Silence. I had a very quick look at the code, and I think pipenv.utils.console.quiet should be set according to the commandline/environment options.