-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
"pipenv requirements" command doesn't export "extras" since version 2023.7.1 #5783
Comments
Same as issue #5780 |
Actually this is maybe a different issue. |
I'm taking a shot a PR now for this issue. |
I've tagged a PR that I think should fix this, if you could have a try and help determine if it still needs work (even added some test cases). |
Thank you very much, you've been so quick ! I try in the day and let you know :) |
Hi @matteius, I confirm that the bug has been corrected with your changes. I see nothing more to add to this issue. Thank you again ! :) |
Description
My problem could be linked to issue 5780.
In one of my projects, I use certain packages with "extras" (django-storages[azure])
Since version 2023.7.1, the pipenv requirements command ignores extras. As a result, the version specified in the Pipfile does not correspond to the version exported by pipenv requirements.
How to reproduct
My Pipfile looks like :
Before version 2023.7.1, pipenv requirements led me to:
And now I only have:
The text was updated successfully, but these errors were encountered: