pre-commit.ci autofix

pre-commit.ci autofix

Hello! Thanks again for following up! I regret to inform you that we currently have limited capacity to review contributions, so it may take some time until we are able to review your PR. We would appreciate your patience.

I take it as there are no publicly available indices that provide RFC 9457 error responses?

Also, it wasn't clear to me from the DPO discussion that is ready for implementation, should this not be a packaging PEP first and gain community consensuses? @pfmoore

I agree, I think we should probably wait until this is a standard before implementing it here. Or at least until PyPI implements it (there's a possibility that PyPI won't wait for a standard, and if something is available in PyPI there's a decent justification for us implementing it anyway - but that would be on a case by case basis).

@luisgcoding thanks for the PR but I'm marking it as draft for now. I guess either:

• PyPI updates it's current non-standard message to said RFC standard (but not Python packaging standard), and we update update pip's logic to reflect that
• Or, a Python packaging PEP is created and accepted and we can implement that

Hello! Thanks again for following up! I regret to inform you that we currently have limited capacity to review contributions, so it may take some time until we are able to review your PR. We would appreciate your patience.

I take it as there are no publicly available indices that provide RFC 9457 error responses?

Thank you for the information @ichard26 . You are right as far as I know there are no public registries that support RFC9457 responses yet.

@luisgcoding thanks for the PR but I'm marking it as draft for now. I guess either:

• PyPI updates it's current non-standard message to said RFC standard (but not Python packaging standard), and we update update pip's logic to reflect that
• Or, a Python packaging PEP is created and accepted and we can implement that

Thanks for the feedback @notatallshaw I understand the concern about implementing this before there's concrete adoption.

A few questions to help me determine the best path forward:

1. Would it be appropriate to propose this to the PyPI maintainers first? If so, what's the best channel for that discussion?
2. Do you know what is the best way to start the conversation about creating a PEP for this?
3. Are there any other considerations I should be aware of when deciding between these approaches?

Happy to keep this as a draft and coordinate with the appropriate stakeholders before moving forward.

I would strongly suggest working towards a standard. Even if PyPI implement this without a standard, I'd be cautious about implementing it in pip (my comment above wasn't intended to endorse the idea of us implementing this without a standard, just to note that it was possible).

There's already a discussion on discuss.python.org, so the process to start working towards a PEP is to continue the discussion there, and offer to write a PEP 🙂