Paul Moore

#10491 seems to have stalled, and no-one else is working on it as far as I am aware.

Because cryptography 44.0.0 is *not* compatible with Python 3.9.0. The index metadata includes `python-requires`, so pip sees that before trying to download, and rejects that version of cryptography. Use `--python-version...

> That I get, but why does 39 resolve to 3.9.0 and not to any available 3.9.X Even if it did mean "any 3.9.X" (which it doesn't), that would still...

The PR looks good, although I’m not a http expert so I can’t comment on details like status and header handling. Like @notatallshaw I wish we could leave this sort...

There isn’t an “approve with conditions” button, but I approve this change on the basis that someone who understands http should check the header and status handling.

@ichard26 WHat's the status on this? It seems close to ready, but there are still some design questions being asked. Is release 25.1 (in a couple of weeks) still a...

> Any thoughts @pfmoore @notatallshaw? I'm going to keep out of the design discussions. I have a bunch of other things on my plate, and not much spare time, so...

@notatallshaw your comment [here](https://github.com/pypa/pip/pull/12991#issuecomment-2770827654) suggested that you still have reservations about this. Is that still the case? If so, how do we resolve this? We have a week, maybe 2...

For the example of specifiers I agree[^1] that this is the intended meaning, and the proposed change is just a textual clarification, which can be done by a PR. For...

OK, I've thought some more about this and changed my mind. There appears to be a lot more subtlety here than I originally thought, and I'm *not* comfortable with simply...