Matt Davis

> Here's more info: https://github.com/pypa/setuptools/issues/4483 I suggest following the guidance in the setuptools issue as my current understanding is your issue is actually occurring in setuptools/packaging and should not be...

Should `pipenv` add `packaging>=22.0` to our pypoject.toml dependencies? Would that solve the issue @viktorvorobev ?

# Issue #6220 Analysis and Proposed Resolution **1. Problem Summary:** The issue highlights a problem with reactivating a Pipenv-created virtual environment after it has been deactivated using the `deactivate` command....

Currently the extras key should be defined, I believe when you run `pipenv install "my_utils[markdown]"` it should be generating the correct Pipfile entry -- its not clear to me from...

Could this issue be checked against this branch? https://github.com/pypa/pipenv/pull/6276

@evan0greenup we don't have that local .git -- Its not clear to me how to test a local .git repository, wouldn't it normally be a local file install?

I am not sure if https://github.com/pypa/pipenv/pull/6242 will change the behavior here, since `git: git+file` is overly verbose I believe `{git = "file://...}"`is preferred over `{git = "git+file://...}`

I just checked and #6242 does not break the existing assumptions -- but I think the confusion with this ticket is when installing a vcs repository from a local file...

After spending a few hours on it tonight and trying to test it and seeing differences in behaviors between git bash and powershell, and also it finding my pyenv versions...

@TBBle -- I rewrote python finder over my lunch break -- it seems to work with pyenv on linux + windows store python installs from registry. https://github.com/pypa/pipenv/pull/6360 replaces this PR.