id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
35980	Make Django release artifacts PEP 625 compliant	Sarah Boyce	Nick Pope	"After the recent security release, I received some email notifications from PyPI:

> This email is notifying you of an upcoming deprecation that we have determined may affect you as a result of your recent upload to 'Django'.
>
> In the future, PyPI will require all newly uploaded source distribution filenames to comply with PEP 625. Any source distributions already uploaded will remain in place as-is and do not need to be updated.
>
> Specifically, your recent upload of 'Django-5.1.4.tar.gz' is incompatible with PEP 625 because it does not contain the normalized project name 'django'.
>
> In most cases, this can be resolved by upgrading the version of your build tooling to a later version that supports PEP 625 and produces compliant filenames.
>
> If you have questions, you can email admin@pypi.org to communicate with the PyPI admin@pypi.org to communicate with the PyPI administrators. 

I believe this relates to: https://github.com/pypi/warehouse/issues/12245
There's a chance that they might stop supporting non-normalized names by ""end of year"": https://github.com/pypi/warehouse/issues/12245#issuecomment-2272378958

I believe the name normalization was also discussed here: https://github.com/django/django/pull/17806#issuecomment-2176465382 hence cc-ing some people involved from that PR

I'm not 100% certain the path forward, it feels to me we might need to make a change and backport to all supported versions and perhaps announce this on the blog. I have no preference, but I need help to know what we should do here."	Cleanup/optimization	closed	Packaging	dev	Normal	fixed		Claude Paroz Natalia Bidart Mariusz Felisiak Tim Graham Carlton Gibson Nick Pope Baptiste Mispelon	Ready for checkin	1	0	0	0	0	0