Matt Davis

@yukihiko-shinoda Could you recheck this behavior on `pipenv=2022.9.4` -- Based on #5130 I am not seeing issues like this anymore on the current version and other users have reported similar.

I just checked `pipenv install pytest pipenv-setup` on windows and linux using `pipenv==2022.9.4`: ``` # Windows "colorama": { "hashes": [ "sha256:854bf444933e37f5824ae7bfc1e98d5bce2ebe4160d46b5edf346a89358e99da", "sha256:e6c6b4334fc50988a639d9b98aa429a0b57da6e17b9a44f0451f930b6967b7a4" ], "markers": "python_version >= '2.7' and python_version not...

> Note that it requires to remove Pipfile.lock, otherwise markers of colorama in Pipfile.lock doesn't remove when pipenv lock even with pipenv ver. 2022.9.24 . @yukihiko-shinoda I must have missed...

@Suraj-Mittal What was the other issue report? In debugging, have you tried re-creating your virtualenv with `pipenv --rm` and `pipenv sync`?

@Suraj-Mittal Please verify that you are on `pipenv==2022.9.8` -- also have you tried the main branch yet?

@Suraj-Mittal Very possible you'll get the same error on main branch, but just in case since there have been a few changes since last release, you could try `pip uninstall...

@Suraj-Mittal Do you happen to have either of these variables set: `echo %PIPENV_SHELL%` `echo %PIPENV_SHELL_FANCY%`

Yes on environment variable. the problem for me debugging this is the stack trace is clear, but the error is not -- I am guessing it cannot find the executable/command...

@Suraj-Mittal Would you be willing to try the same thing using Windows Power Shell just to see if its different? Also, I just sent a Suraj Mittal a message on...

One thing we will have to be particularly careful about, because having just two categories of `dev` and `packages` is that constraints of packages have to be supplied when resolving...