#35980: PyPI will require uploaded source distribution filenames to comply with
PEP
625 and contain the normalized project name "django"
--------------------------------------+------------------------------------
Reporter: Sarah Boyce | Owner: (none)
Type: Cleanup/optimization | Status: new
Component: Core (Other) | 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
--------------------------------------+------------------------------------
Comment (by Baptiste Mispelon):
> AFAIR, we refrained from using a recent setuptools with requires =
["setuptools>=61.0.0,<69.3.0"], to avoid that change (Django to django).
Yes, that was done in this merge request:
https://github.com/django/django/pull/17806#issuecomment-2176465382
I've just tried to build with the latest setuptools (`python -m pip
install build twine && python -m build` from a clean checkout of the git
repo) and it creates two files:
* django-5.2.dev20241206115354.tar.gz
* Django-5.2-py3-none-any.whl
The inconsistent naming seems to be a bug in setuptools [1] (mentionned in
the comment on the patch I linked above).
My opinion is that we should be using the latest version of setuptools and
let it generate the filenames for the builds. Those filenames are internal
plumbing and are not normally exposed to users. They also don't change how
Django is installed when using tools like pip, since those tools will
normalize names internally as well.
One hitch with this plan is that the current release documentation (both
the public one and I assume the ad-hoc scripts used by the fellows) makes
assumptions about those filenames that would not hold true anymore.
[1] https://github.com/pypa/setuptools/issues/3777
--
Ticket URL: <https://code.djangoproject.com/ticket/35980#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701939d4a8999-63e02e05-e320-47c6-b81e-aeb7f11310e8-000000%40eu-central-1.amazonses.com.
