1
0
mirror of https://github.com/django/django.git synced 2024-12-22 17:16:24 +00:00

Fixed #35980 -- Updated setuptools and project name.

This commit is contained in:
Nick Pope 2024-12-06 18:32:39 +00:00
parent 1860a1afc9
commit 7411a45a6b
2 changed files with 5 additions and 5 deletions

View File

@ -480,7 +480,7 @@ Now you're ready to actually put the release out there. To do this:
$ python -m venv django-pip-tarball
$ . django-pip-tarball/bin/activate
$ python -m pip install https://www.djangoproject.com/m/releases/$MAJOR_VERSION/Django-$RELEASE_VERSION.tar.gz
$ python -m pip install https://www.djangoproject.com/m/releases/$MAJOR_VERSION/django-$RELEASE_VERSION.tar.gz
$ django-admin startproject test_tarball
$ cd test_tarball
$ ./manage.py --help # Ensure executable bits
@ -492,7 +492,7 @@ Now you're ready to actually put the release out there. To do this:
$ python -m venv django-pip-wheel
$ . django-pip-wheel/bin/activate
$ python -m pip install https://www.djangoproject.com/m/releases/$MAJOR_VERSION/Django-$RELEASE_VERSION-py3-none-any.whl
$ python -m pip install https://www.djangoproject.com/m/releases/$MAJOR_VERSION/django-$RELEASE_VERSION-py3-none-any.whl
$ django-admin startproject test_wheel
$ cd test_wheel
$ ./manage.py --help # Ensure executable bits
@ -517,7 +517,7 @@ Now you're ready to actually put the release out there. To do this:
#. Go to the `Add release page in the admin`__, enter the new release number
exactly as it appears in the name of the tarball
(``Django-<version>.tar.gz``). So for example enter "4.1.1" or "4.2rc1",
(``django-<version>.tar.gz``). So for example enter "4.1.1" or "4.2rc1",
etc. If the release is part of an LTS branch, mark it so.
__ https://www.djangoproject.com/admin/releases/release/add/

View File

@ -1,9 +1,9 @@
[build-system]
requires = ["setuptools>=61.0.0,<69.3.0"]
requires = ["setuptools>=69.3.0"]
build-backend = "setuptools.build_meta"
[project]
name = "Django"
name = "django"
dynamic = ["version"]
requires-python = ">= 3.10"
dependencies = [