Matt Davis

@lewiswolf Just cut release `2023.10.3` which has all the changes from main -- I am not convinced that it will solve your issue, but worth having a check. If its...

@mjhalwa Unfortunately I don't see the system PATH in the support info, so I only have to go by that you added it to the path -- it should find...

@bjorn-verstrepen If possible, please check this against: https://github.com/pypa/pipenv/pull/5793

@bjorn-verstrepen Actually nevermind, I just cut a new release with that branch I referenced -- if you could check `2023.8.19` instead, it would be helpful. Thank you!

Hmmm, well this actually seems like possibly a pip bug, but with my proposal in https://github.com/pypa/pipenv/pull/5935 would allow you to specify the target python version and system (basically anything in...

Ah sorry, I had linked the wrong PR: https://github.com/pypa/pipenv/pull/5931 You would add a section to the Pipfile named resolver, example: ``` [resolver] python_full_version = "3.7.13" python_version = "3.7" finder_python =...

The problem with my branch is that I suspect the lock file was adjusted correctly based on the overrides, but during install the markers get evaluated again against the actual...

> I've considered modifying pipenv, but it seems over the top. Well that is the best way to have it fixed -- this isn't a priority for me, so opening...

> we also found that having setuptools 68.2.0 w/ pipenv 2023.7.11 installed also seems to trigger this behavior (68.0.0 works correctly) That sounds likely related. I found this PR that...

@ChannyClaus I opened a PR that I believe addresses it. https://github.com/pypa/pipenv/pull/6006 I don't think you'll need to pass `--no-deps` since we already pass this as part of pipenv installation.