Matt Davis

@stewartmiles Hmmm, this is a case where I would recommend created a prereq category for things like setuptools: `pipenv install setuptools --categories=prereq` and then install that category first so that...

default packages constraints do constrain all other categories, but that is about it, yeah they are otherwise locked independently. > would it make sense to parse the build requirements (i.e...

Another thing to factor into it is the install phases, each phase technically you would think of as 1 pip install phase, but its actually up to 2 because hash...

> If one editable install has a build time dependency upon another, pip install --no-deps fails. That is where named package categories can be useful, because you can stage your...

Last comment for now though would be around setuptools -- you mentioned pinning the version and having to periodically update it -- why not just pin to star unless you...

Ok most recent thing I discovered that is an issue with todays release is: https://github.com/pypa/pipenv/pull/5926 Not sure if it impacts what you were seeing at all, but I bring it...

Worth checking with https://pypi.org/project/pipenv/2023.9.8/

@stewartmiles might be worth trying todays release just in case there was an issue resolving the specific build requirement/dependency, since ignore_compatibility was defaulted to True in yesterdays release. That being...

@stewartmiles It appears to only be an issue with using `--skip-lock` ``` matteius@matteius-VirtualBox:~/pipenv_editable_install_repro$ cat Pipfile [[source]] url = "https://pypi.org/simple" verify_ssl = true name = "pypi" [packages] requires-setuptools1 = {file =...

Worth noting too that I had to modify install.sh by moving it up a directory and commenting out the cd line, because it was getting into a circular import otherwise.