Matt Davis

@jfly sorry for being dense but is this still an issue?

@n1ngu and @duailibe Could you recheck with `pipenv==2022.1.8` and if that still doesn't work we have a branch that upgrades to `pip==22.0.4` which is `vendor-pip-22.0.3-followup-changes` Could you try those?

@n1ngu So at first look, and some background is that the locking/resolution/installation phase has all ben converted over to use pip internals. So with pip just trying to install package...

Can the assumptions and behavior of this ticket be rechecked with `pipenv==2022.4.20`?

This should be resolved now on `pipenv==2022.8.19`

@n1ngu That is odd, I agree your example is still experiencing an issue, but we have a very similar example that does work now: https://github.com/pypa/pipenv/issues/4323 I haven't seen why your...

@n1ngu It works in `2022.8.19` if you mark the packages as editable in your `Pipfile`: ``` matteius@matteius-VirtualBox:~/pipenv-triage/pipenv-issue-4553$ git diff diff --git a/Pipfile b/Pipfile index 1f91e94..12867d4 100644 --- a/Pipfile +++ b/Pipfile...

I believe this should be resolved, could you checked @hlongmore ?

The original error posted by @spott was a `pip` error -- but we are on the latest `pip=22.2.2` now which certainly supports this case -- I am willing to reopen...

Amazingly zero tests broke by removing that validation crud. TODO -- Check on the exception classes that were being raised if they are still being used anywhere. TODO -- Solve...