Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove outdated "single sourcing package version" advice #1276

Open
wants to merge 7 commits into
base: main
Choose a base branch
from
Open
1 change: 0 additions & 1 deletion source/guides/section-build-and-publish.rst
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,6 @@ Building and Publishing

writing-pyproject-toml
distributing-packages-using-setuptools
single-sourcing-package-version
dropping-older-python-versions
packaging-binary-extensions
packaging-namespace-packages
Expand Down
173 changes: 0 additions & 173 deletions source/guides/single-sourcing-package-version.rst

This file was deleted.

7 changes: 3 additions & 4 deletions source/guides/writing-pyproject-toml.rst
Original file line number Diff line number Diff line change
Expand Up @@ -110,8 +110,8 @@ similar. In such cases, you should mark the field as dynamic using, e.g.,


When a field is dynamic, it is the build backend's responsibility to
fill it. Consult your build backend's documentation to learn how it
does it.
fill it. Consult :ref:`Single sourcing the version discussion` for more
details.


Basic information
Expand Down Expand Up @@ -163,8 +163,7 @@ This field is required, although it is often marked as dynamic using
dynamic = ["version"]

This allows use cases such as filling the version from a ``__version__``
attribute or a Git tag. Consult :ref:`Single sourcing the version` for more
details.
attribute or a Git tag.


Dependencies and requirements
Expand Down
Loading