Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restore this message as stderr because it affects requirements.txt generation #5005

Merged
merged 4 commits into from
Mar 23, 2022

Conversation

matteius
Copy link
Member

@matteius matteius commented Mar 23, 2022

The issue

The fix

Restore the logging back to be stderr.

The checklist

  • Associated issue
  • A news fragment in the news/ directory to describe this fix with the extension .bugfix, .feature, .behavior, .doc. .vendor. or .trivial (this will appear in the release changelog). Use semantic line breaks and name the file after the issue number or the PR #.

@oz123 oz123 merged commit 7f05d65 into main Mar 23, 2022
@oz123 oz123 deleted the issue-5003-pipenv-dot-env-loading-message branch March 23, 2022 14:22
@sdepablos
Copy link

@matteius does this solve any use case when the output of any pipenv command is redirected to a file. We found ourselves with the same issue when doing pipenv run

@matteius
Copy link
Member Author

matteius commented Mar 23, 2022

@sdepablos Yes, this was only affecting pipenv run my earlier messages said install which was misleading but was what I thought initially this AM. Since we changed it back to stderr it won't be redirected to the file because that only captures stdout. Also, planning to issue a new release tonight to patch up the two known regressions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants