Matt Davis

@frostming That makes sense, thanks. I was getting tripped up because I moved my generated Pipfile and Pipfile.lock down a directory into the sphinx and tried running `pipenv install -e...

@PythonCoderAS are we in agreement that its not a bug, can I close this issue without complaints?

@PythonCoderAS I agree the actual error message is somewhat cryptic because it says `RequirementError: Failed parsing requirement from '` when it really was a failure to even find a setup.py...

@PythonCoderAS please see frostming's last comment. If this is an important improvement to you, please open the issue with the requirementslib backlog and consider what the change would look like...

Index restricted packages changed this some -- https://pipenv.pypa.io/en/latest/advanced/#specifying-package-indexes at least for the resolve phase, which sets the packages hashes. The recent batch install phase optimization does install from all indexes,...

This should be resolved with the latest release `2022.11.5`

I don't think there should be a v in front of your version for 2022.4.20 on the solution line `RUN pip3 install pipenv==v2022.4.20` -- not sure how that could work....

@oz123 I am wondering what could have been different between `2022.4.20` and `2022.4.21` that might have caused this?

Ah I forgot that I updated the minimum version of pip and setuptools when I dropped 3.6 support -- I think I based it on the versions that had dropped...

I would like some guidance on what the proper resolution would be for pipenv -- should we loosen the versions of setuptools in the setup.py? I am not convinced that...