Re: [Django] #35980: Make Django release artifacts PEP 625 compliant (was: Make Django binaries PEP 625 compliant)

[Django]

#35980: Make Django release artifacts PEP 625 compliant
-------------------------------------+-------------------------------------
Reporter: Sarah Boyce | Owner: Natalia
Type: | Bidart
Cleanup/optimization | Status: assigned
Component: Packaging | Version: 5.1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):

* summary: Make Django binaries PEP 625 compliant => Make Django release
artifacts PEP 625 compliant

Comment:

After lots of reading, I think we are dealing with a mix of issues. The
PyPI deprecation warning is only about the tarball, not about the wheel
name. Specifically, there are two relevant PEPs:

* PEP 625, which addresses naming conventions for source distributions,
and
* PEP 491, which addresses naming conventions for wheels.

As Baptiste said in comment:4, current `setuptools` (`75.6.0`) produces
lowercase `django` tarball and capitalized `Django` wheel. If we proceed
with this as-is, we would resolve the "PyPI warning" for the source
distribution, addressing that part of the issue. However, we'd still need
smart tools and a flexible download page to handle both naming formats. I
think this is doable and would allow us to "detach" ourselves from the
pressure of solving the wheel naming inconsistency from external sources.
--
Ticket URL: <https://code.djangoproject.com/ticket/35980#comment:11>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.