Feature request: Add a --quiet/-q option to pipenv run.

When you have an .env file in your project directory, pipenv run will output Loading .env environment variables… before the actual script output. This is undesirable if you need to parse the output of pipenv run ... in a script. Therefore, a --quiet option that suppresses such output would be nice.

[stellarhoof]

@techalchemy Why? That is not an error and it will make life harder for those who want to actually see errors. Say you’re working on a script but don’t want to see that message, so you redirect stderr somewhere else and now you can’t see any errors at all.

[bbbart]

perhaps this is a valid use case for the --quiet option?

I have the following line in my .vimrc on which I rely a lot:

map <F1> mx<cr>:%!pipenv run black --line-length 79 --safe --quiet -<cr>x`

Hitting F1 either showed my basic syntax or other errors black output at the bottom of my source file, or it beautified my code. Now with an .env file in my project, I am forced to change this line to

map <F1> mx<cr>:%!pipenv run black --line-length 79 --safe --quiet - 2>/dev/null<cr>x`

(which now applied to all my projects!) and the usefulness has been reduced, since black can’t tell me any longer if it has problems parsing my code.

I’d much rather be able to say

map <F1> mx<cr>:%!pipenv --quiet run black --line-length 79 --safe --quiet -<cr>x`

or something like that.