Matt Davis

@FlavioAmurrioCS `2024.3.0` release has been cut with these improvements.

Its possible I missed porting a relevant patch over when we did the pip upgrade, or that something else changed there that could have affected it. I will dig more...

I think I see the issue -- the `ignore_compatability_finder` patch did not get properly ported to the new pip version.

@FlavioAmurrioCS could you check against: https://github.com/pypa/pipenv/pull/6426

Analysis for Issue #6267: ## Analysis of Pipenv Issue #6267 **1. Problem Summary:** The issue describes a performance regression in Pipenv 2024.0.0, where the `pipenv install` command, even when installing...

fyi -- Testing out some Gen AI code analysis of recent issues

@fredcohen-aa `2024.0.3` is working better for vcs (assuming you aren't using env vars), but also what you are reporting is slightly different than a vcs issue though it seems to...

I think this is going to be challenging issue as we move forward with pip >= 24.1.2 it appears to be more strict about some things such as version specifiers....

@fredcohen-aa please open a different issue report for what you are seeing with even more details than you provide above.

Analysis for Issue #6266: ## Analysis of Pipenv Issue #6266 **1. Problem Summary:** The core problem is that Pipenv's resolver in version 2024.1.0 mistakenly attempts to resolve VCS dependencies as...