Replace deprecated pipenv lock with pipenv requirements#7764
Conversation
9485c02 to
dcc729c
Compare
In the versions between what we are currently on in `dependaobt-core` and the latest versions of `pipenv`, they deprecated and then completely removed the `pipenv lock [-d]` command in favor of `pipenv requirements [--dev]` command. Since our current version of `pipenv` supports the `pipenv requirements` command, let's proactively switch to it now. That will make the future upgrade in #7715 easier. More context: * pypa/pipenv#5069 * pypa/pipenv#5091 * pypa/pipenv#5198 * pypa/pipenv#5200
dcc729c to
5a57cbf
Compare
|
BTW @matteius it was a little painful to track this down. I'm all for deprecations and even removing functionality, but maybe leave the deprecation message around a little longer? Our current version is less than two years old and in that time it was deprecated, but then the warning was also removed... would have been nicer if The other way this is typically done is with SemVer where I can look at the major version release notes to see the breaking changes. But that wasn't possible since Just a suggestion. |
|
Thanks for the feedback @jeffwidman -- I think that is a reasonable request we can try to accommodate going forward. CC @oz123 |
In the versions between what we are currently on in
dependaobt-coreand the latest versions ofpipenv, they deprecated and then completely removed thepipenv lock [-d]command in favor ofpipenv requirements [--dev]command.Since our current version of
pipenvsupports thepipenv requirementscommand, let's proactively switch to it now. That will make the future upgrade in #7715 easier.More context:
install -rflag for generatingrequirements.txtpypa/pipenv#5198