Matt Davis

The resolver uses the virtualenv python version, which will be what pip uses to resolve packages against.

@matejsp you got me thinking about some possible workarounds to these types of issues, and I have opened a draft PR of something I have been playing with: https://github.com/pypa/pipenv/pull/5931 This...

@matejsp I couldn't get the version ranges to work reasonable well with a first pass because it required me to change how the markers evaluate, and I learned its quite...

@klausmyrseth I believe the support added last Fall for named package categories basically suites this use case you describe.

@kalebmckale I think it makes sense, feel free to open a PR.

> * It deletes all whitespaces making pipfile very unreadable and hard to revert all the corruption before committing. We gave up on trying to preserve the comments/whitespace in the...

@bblanchon you might be interested in my very recent work on an `pipenv upgrade` command -- https://github.com/pypa/pipenv/pull/5617 Its my answer to getting rid of `--keep-outdated` and `--selective-upgrade` and probably replaces...

@bblanchon `pipenv update` does something very different from what `pipenv upgrade` does, and I am not convinced to replace `update` with the functionality of `upgrade` yet so hence prototyping a...

Plus that branch removes one of the flawed validation checks on the `--system` flag . What is it that the `update` command does that is desirable? Its one of the...

I've taken a stab at updating the `update` command as well -- it doesn't yet address your concerns about the `--system` flag but its heading in the right direction towards...