-
Notifications
You must be signed in to change notification settings - Fork 293
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
Plugin not compatible with =>2022.8.13 of pipenv #716
Comments
I'd recommend calling I'm now doing this manually before calling |
A temporary workaround to solve this issue is to install the plugin through the PR branch with
|
Hey, I've added a PR to fix an issue I've hadd with git packages being the sources. |
I'm closing as #718 should resolve the issue |
Issue Description
Currently the plugin is not compatible with any version of
pipenv
> 2022.8.13 as they have changed how therequirements.txt
command is used.The plugin currently calls
pipenv lock --requirements --keep-outdated
and starting with 2022.8.13 they have removed the -requirements and --keep-outdated flags and consolidated topipenv requirements
.Not blaming the plugin as this seems like a very dumb and breaking change on part of the maintainers of
pipenv
.The current workaround I have employed to my company's codebases is to set the install step of pipenv to use version 2022.8.5, as it is the last with the old syntax usage:
Per their documentation:

The text was updated successfully, but these errors were encountered: