PEP 710: state download_info structure used in pip

[fridex]

---

📚 Documentation preview 📚: https://pep-previews--3880.org.readthedocs.build/

[fridex]

@sbidoul @pfmoore @sethmlarson following discussion in pypa/pip#11865 (comment), I was not sure about the phrasing here, also whether this should go to the specification section. Any suggestions are welcome.

[pfmoore]

I'm a strong -1 on the standard special casing pip in any way.

[fridex]

I'm a strong -1 on the standard special casing pip in any way.

Okay, sounds reasonable.

Addressing comment pypa/pip#11865 (comment), @sbidoul Is it okay if we keep PEP as-is with the generic cache note, without stating the download_info structure? Maybe I missed something here otherwise.

[pfmoore]

Please raise this on Discourse, and in particular get input from the uv developers, who aggressively cache a lot of things for performance, and for whom this requirement might be problematic.

[fridex]

Please raise this on Discourse, and in particular get input from the uv developers, who aggressively cache a lot of things for performance, and for whom this requirement might be problematic.

They were notified in astral-sh/uv#5627

As we do not want to have pip-specific parts in the specification, closing this PR, and let's continue with the discussion on Discourse.

[sbidoul]

Addressing comment pypa/pip#11865 (comment), @sbidoul Is it okay if we keep PEP as-is with the generic cache note, without stating the download_info structure? Maybe I missed something here otherwise.

@fridex sure, I also think it's better not to mention download_info in the PEP, as that is pip-specific.