pipenv lock -r deprecation should be sent to stderr

[mgmarino]

Issue description

As of 2022.4.30, the command pipenv lock -r has become deprecated. The problem is that the deprecation message breaks current code since the previous way to use this was:

pipenv lock -r > requirements.txt

Since the deprecation message gets sent to stdout, this results in a requirements.txt file that fails when used by pip. The deprecation message should rather go to stderr where it will:

• be seen by users
• not break requirements.txt

---

[matteius]

#5091

[mgmarino]

Thanks @matteius, I missed that there was an open PR (just searched the issues)!

[matteius]

@mgmarino no worries, I just merged in the PR to main and going to close this out for now. It will be in the next release, which I am not 100% sure on when that will be, but sometime this month.