Matt Davis
Matt Davis
I pushed a change to the future looking pipenv branch which get the `-v` flag working with the pip resolver again in a more expected way: https://github.com/pypa/pipenv/pull/5793
I believe the new release solves this.
Analysis for Issue #5823: ## Analysis of Pipenv Issue #5823: Missing info for package conflict ### 1. Main Problem The issue reports that Pipenv sometimes fails to provide enough information...
@oz123 it seems this issue still stands, it doesn't reject keys that aren't utilized.
The easier question first -- you'd have to fork to create a branch and open a PR. IIRC correctly, the functionality was removed to fulfill the idea that all specifiers...
I think the problem with `--lock-only` was that subsequent actions would revert back whatever sub-dependency without it originating from a proper specifier somewhere in the Pipfile. It could be added...
I think when I removed requirementslib I broke something with canonical naming, and I could use help figuring out the right patch. There was this, but apparently its still an...
@Kroppeb could this be checked against `2024.2.0` or even https://github.com/pypa/pipenv/pull/6282
We accept contributions -- I don't exactly know because I don't even have an API key for it now that pyup.io has gone to a fully paid model.
`2026.0.1` will have some enhancements (already in main) + we adopt `pipenv audit` with is `pip-audit` for the free open model.