Dan Ryan

To be clear -- you obviously will need the internet or a fully mocked index to actually use the resolver backing requirementslib. As a consequence of doing resolution this also...

@jayvdb that would be lovely, sadly I work far too much on pipenv related projects as is and my employer definitely doesn't care if I continue spending my time on...

So currently, passa locks `pip-shims` to that marker as well, which simply isn't true. Parents shouldn't inherit the markers of their children, the relationship should only flow in the other...

> Say I’m running Python 2.7, and have a package specifying this dependency: >``` > django >= 2.0; python_version >= '3.7' >``` > What version of Django should it resolve...

is this for resolution or for creating a requirement? IF the latter, what doesn't work atm?

you're talking about `pyproject.toml` style implementations though right? Pep 345 metadata is already parsed somewhere, I just need to see an example project that has it implemented

FYI I am going to add some tests on top of this and merge it if you don't have any issues, since this makes it a lot easier to test...

No worries I don’t think I changed any functionality just moved stuff around. But if you want to release a patch release of master (or I can if you’re ok...

I believe we need to clean it before we build the wheel

oh yeah to summarize what we talked about whenever that was, and the reason why we have the custom cleaning stuff in pipenv, `Requires-Python: 3` is completely valid for example