Allow more control over .env loading message

[mjpieters]

I'm running automated pipenv run ... commands, and each and every time there is a Loading .env environment variables message.

Please, let me disable that message. pipenv run doesn't take switches nor is there a PIPENV_BARE environment variable, and so output of the message is unconditional.

Either support --bare for pipenv run, or better still, let me control pipenv output with an environment variable like PIPENV_BARE or PIPENV_QUIET.

What I don't want:

• Having to disable .env loading with PIPENV_DONT_LOAD_ENV
• Having to redirect stderr to /dev/null; the commands I run with pipenv run have to be able to use stderr too, and if the .env is corrupted or PIPENV_DOTENV_LOCATION is set I don't want error messages about those issues to be missed.

[264nm]

Second this one...

[teroyks]

A third from me.

[codl]

It seems that since 2022.3.23 the message is printed regardless of the presence of a .env file, and on stdout instead of stderr, making this even more of an issue

[project0]

Super annoying, this just broke some CI pipelines for us.

[matteius]

@codl and @project0 Actually there is another issue report of this affecting requirements.txt generation so its a higher priority than I indicated prior and its out for PR now if you would have a look -- I adjusted it to only print the statement if the .env file is present. Can you check if the linked PR branch suites your needs?

[matteius]

In the linked PR #5006 its based on a separate PR to move this back to stderr and only when the .env file exists. Plus in the linked PR you can pass the --quiet flag

matteius@matteius-VirtualBox:~/pipenv-triage/pipenv-4467$ pipenv run echo "TEST" --quiet
Loading .env environment variables...
TEST --quiet

matteius@matteius-VirtualBox:~/pipenv-triage/pipenv-4467$ pipenv --quiet run echo "TEST"
TEST

matteius@matteius-VirtualBox:~/pipenv-triage/pipenv-4467$ export PIPENV_QUIET=1
matteius@matteius-VirtualBox:~/pipenv-triage/pipenv-4467$ pipenv run echo "TEST"
TEST

[matteius]

The fix for this has been released under pipenv==2022.3.24

[nomis]

The fix for this has been released under pipenv==2022.3.24

When PIPENV_QUIET=1 it doesn't load the .env file at all...

[matteius]

Thanks @nomis waiting on an upstream setuptools issue affecting the CI to get sorted before we can merge the fix into main

[Flimm]

The fix for this has been released under pipenv==2022.3.24

When PIPENV_QUIET=1 it doesn't load the .env file at all...

That bug was fixed here: #5010