[14:02:24] <toad_polo> pradyunsg: I'm having a bit of a crazy idea and I'm wondering if you can save me a bit of time - do you know how `pip` determines what version of Python is running it for the purposes of dependency resolution and environment?
[14:03:38] <toad_polo> I want to write a little script that generates a `constraints.txt` that is valid for all my test environments on all my platforms.
[14:04:32] <toad_polo> But doing so I think is actually quite annoying because I think you have to install the entire dependency tree and just observe what got installed (this is apparently what `pip-compile` does).
[14:05:37] <toad_polo> I'm wondering how bad it would be if I fudged it by mocking that out or by modifying `pip` to take those values from an environment variable.
[14:49:00] <sumanah> hey woodruffw! I'm writing my fortnightly update for https://discuss.python.org/t/pypi-security-work-multifactor-auth-progress-help-needed/1042/26 and I see you have updated https://github.com/pypa/warehouse/pull/6084 so it does not say WIP anymore
[14:50:05] <sumanah> woodruffw: is now a good time for other Warehouse developers to give it a go and give you more reviews?
[14:50:43] <woodruffw> sumanah: yep! it should be ready for others to try out, with the usual caveat that the UI is barebones :-)
[14:51:19] <sumanah> woodruffw: ok! mind saying that in a comment on the PR?
[15:31:11] <pradyunsg> toad_polo: pip calls pip._vendor.packaging.markers:Marker.evaluate for the ones in the markers. The source of truth for that -- platform.python_version() -- is also used when checking python_requires elsewhere.