Matt Davis

I believe this is resolvable now -- but let me know if its still an issue on `pipenv==2022.8.19`

@Alexander-Serov if I recall correctly, with the current behavior the secrets needs to be specified in env vars referenced by `PIP_INDEX_URL` and not within `PIP_INDEX_URL` directly -- similar to what...

This is known -- the way index package restrictions was implemented (to prevent package confusion attacks) always defaults unspecified package indexes to the first index in the Pipfile.

Well are you mirroring packages from pypi in your private source?

I've usually been able to narrow it down by looking at the output of the lock generation when using the `-v` or `--verbose` flag.

@sonyakun I think the problem is the egg fragment which is a deprecated or removed syntax -- I just tried with: ``` matte@LAPTOP-N5VSGIBD MINGW64 ~/Projects/pipenv-triage/issue-6095 $ pipenv install git+https://github.com/lithum-labs/dispander.git Creating...

@joaomcarlos > This is extremely confusing. What I think it should be (and already is ... for the most part): > install should just install dependencies pinned on the pipfile.lock....

> the intention of what I said is not to describe what it DOES, but rather what the commands SHOULD do based on the combination of words in them. @joaomcarlos...

@januszm I believe now that we are planning semver releases, the next **major** release we are hoping to switch the behavior of `pipenv install` to be what every non-seasoned user...

Laugh all you want, but I've really been doing my best to drive this project forward in my spare time. I have been using pipenv for about 2-years and 2-months...