Matt Davis

@Askaholic Maybe, but I just retried and got similar results: ``` matteius@matteius-VirtualBox:~/pipenv-triage/issue-5597$ pipenv --rm Removing virtualenv (/home/matteius/.virtualenvs/issue-5597-i00VrxRT)... matteius@matteius-VirtualBox:~/pipenv-triage/issue-5597$ rm Pipfile* matteius@matteius-VirtualBox:~/pipenv-triage/issue-5597$ vim Pipfile matteius@matteius-VirtualBox:~/pipenv-triage/issue-5597$ pipenv --site-packages install Creating a virtualenv...

I can try it with the Dockerfile when I get more time -- on average it adds more time to reproducing an issue than it helps me with, but in...

We recently upgraded to the latest pipdeptree and it has the same behavior -- I asked GPT about this: >You're correct, pipdeptree only lists the packages and their dependencies installed...

Duplicate of this from last week: https://github.com/pypa/pipenv/issues/6151

Since removing requirementslib dependency, it would actually be relatively straight forward to add a name override now.

@tucked `pipenv check` is deprecated technically as its the old deprecated safety check command, and they have migrated to scan which requires an API key. We have addressed that in:...

I am still now trying to track down a possible regression in this branch where by some methods that took 3 params before now think they take 4 (and I...

>However, if I add private_repo = {version="*", index="private"} to the dev list it will succeed. This is expected, as you have your default index as pypi and the package groups...

Any documentation on the topic lives here: https://pipenv.pypa.io/en/latest/indexes/ The docs probably stands to be improved, but the problem with the named package categories (in this case default and dev), is...

@kalebmckale the only category the constraints the other categories currently is the `default` one -- some people have complained on both sides of this which makes me think that should...