[08:21:07] <graingert> looking to move local_scheme def into a declarative setup.cfg
[19:50:46] <kmohrf> hi there :)! I wanted to talk about issue #4783 and the associated PR #5950, though I’m not entirely sure if the discourse forum is better suited (feel free to point that out in case it is). Both issues are currently closed because the original authors lost interest or the specific use case was missing.
[19:50:54] <kmohrf> I’m a frequent user of dh-virtualenv that builds virtualenvs as debian packages. I try to limit my project depencies to packages that are available in Debian, but that’s not feasible in any case. pip’s behaviour of checking system packages first comes in handy because the virtualenv will only include dependencies that do not match the version requirements in my setup.py. One thing I noticed when I got rid of my requirements.txt fi
[19:50:54] <kmohrf> n favor of setup.py’s install_requires is that my own project ended up in the virtualenv. That was unexpected and not what I wanted, though I understand what’s happening. Multiple people suggested the -e flag, but as far as I can see it is advertised as "development mode" so I’m not sure it’s a good fit, as the virtualenv is used in production. --deps-only (or --only-deps to stick with --no-deps naming scheme) would be a helpful
[19:50:55] <kmohrf> ition to solve my use case. Is that something you would consider out of scope for pip or is a new issue the way to go forward? Are there any other remarks you might have?
[20:26:43] <pradyunsg> kmohrf: which project are those issue numbers from?