Merge branch 'main' into feature/remove-more-pkg_resources

Author: jaraco

.bumpversion.cfg

@@ -1,5 +1,5 @@
 [bumpversion]
-current_version = 80.8.0
+current_version = 80.9.0
 commit = True
 tag = True
 

.github/workflows/main.yml

@@ -42,7 +42,7 @@ jobs:
       matrix:
         python:
         - "3.9"
-        - "3.13"
+        - ">=3.13.5"  # temporary bound until it becomes the default, python/cpython#135151
         platform:
         - ubuntu-latest
         - macos-latest
@@ -157,6 +157,7 @@ jobs:
     if: always()
 
     needs:
+    - check-changed-folders
     - integration-test
     - test
     - collateral
@@ -228,6 +229,38 @@ jobs:
             VM-${{ matrix.platform }},
             Py-${{ steps.python-install.outputs.python-version }}
           token: ${{ secrets.CODECOV_TOKEN }}
+            
+  check-changed-folders:
+    name: Fail the job if files changed under _disutils/_vendor folders
+    if: github.event_name == 'pull_request'
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+      - name: Check if files changed in the _distutils folder
+        id: changed-files-specific-distutils
+        uses: tj-actions/changed-files@v34
+        with:
+          files: |
+            setuptools/_distutils/**
+      - name: Check if files changed in the _vendor folder
+        id: changed-files-specific-vendor
+        uses: tj-actions/changed-files@v34
+        with:
+          files: |
+            setuptools/_vendor/**
+      - name: Fail the job if any file(s) in the _distutils folder change
+        if: steps.changed-files-specific-distutils.outputs.any_changed == 'true'
+        run: |
+          echo "One or more files in the setuptools/_distutils folder has changed." | tee "${GITHUB_STEP_SUMMARY}"
+          exit 1      
+      - name: Fail the job if any file(s) in the _vendor folder change
+        if: steps.changed-files-specific-vendor.outputs.any_changed == 'true'
+        run: |
+          echo "One or more files in the setuptools/_vendor folder has changed." | tee "${GITHUB_STEP_SUMMARY}"
+          exit 1 
 
   integration-test:
     needs: test

.pre-commit-config.yaml

@@ -1,6 +1,6 @@
 repos:
 - repo: https://github.com/astral-sh/ruff-pre-commit
-  rev: v0.9.9
+  rev: v0.12.0
   hooks:
   - id: ruff
     args: [--fix, --unsafe-fixes]

NEWS.rst

@@ -1,3 +1,13 @@
+v80.9.0
+=======
+
+Features
+--------
+
+- Set a deadline for the removal of pkg_resources later this year (December). (#3085)
+- Removed reliance on pkg_resources in test_wheel. (#3085)
+
+
 v80.8.0
 =======
 
@@ -671,7 +681,7 @@ v72.2.0
 Features
 --------
 
-- Merged with pypa/distutils@b7ee725f3 including: Support for Pathlike objects in data files and extensions (pypa/distutils#272, pypa/distutils#237), native support for C++ compilers (pypa/distuils#228) and removed unused get_msvcr() (pypa/distutils#274). (#4538)
+- Merged with pypa/distutils@b7ee725f3 including: Support for Pathlike objects in data files and extensions (pypa/distutils#272, pypa/distutils#237), native support for C++ compilers (pypa/distutils#228) and removed unused get_msvcr() (pypa/distutils#274). (#4538)
 
 
 v72.1.0

docs/userguide/interfaces.rst

@@ -50,6 +50,16 @@ reserve the right of speeding up the deprecation cycle and shortening deprecatio
 Note that these are exceptional circumstances and that the project will
 carefully attempt to find alternatives before resorting to unscheduled removals.
 
+.. important::
+   In the context of ``setuptools``, the introduction of :py:mod:`warnings`
+   (including deprecation warnings) is not considered a breaking change *per se*.
+   Instead it is considered a backwards compatible *communication action* that
+   precedes an upcoming breaking change. This is becauset code
+   containing warnings typically does not fail and can successfully terminate
+   execution, unless users explicitly opt into transforming those warnings
+   into errors (e.g., via Python's :external+python:ref:`-W option or
+   PYTHONWARNINGS environment variable <using-on-warnings>`).
+
 
 What to do when deprecation periods are undefined?
 --------------------------------------------------
@@ -147,7 +157,7 @@ you can still resort to restricting the version of Setuptools to be installed.
 This usually includes modifying ``[build-system] requires`` in ``pyproject.toml``
 and/or specifying ``pip`` :external+pip:ref:`Constraints Files` via
 the ``PIP_CONSTRAINT`` environment variable (or passing |build-constraint-uv|_).
-Please avoid however to pre-emptively add version constraints if not necessary,
+Please avoid however to preemptively add version constraints if not necessary,
 (you can read more about this in https://iscinumpy.dev/post/bound-version-constraints/).
 
 .. |build-constraint-uv| replace:: ``--build-constraint`` to ``uv``

newsfragments/3085.feature.rst

@@ -0,0 +1 @@
+Remove post-release tags on setuptools' own build.

newsfragments/4530.feature.rst

@@ -0,0 +1 @@
+Avoid repeated calls to ``str.startswith`` and ``str.endswith``.

newsfragments/5033.misc.rst

@@ -10,7 +10,7 @@ backend-path = ["."]
 
 [project]
 name = "setuptools"
-version = "80.8.0"
+version = "80.9.0"
 authors = [
 	{ name = "Python Packaging Authority", email = "[email protected]" },
 ]

pyproject.toml

@@ -85,3 +85,7 @@ filterwarnings=
 
 	# Ignore warnings about consider_namespace_packages (jaraco/skeleton@6ff02e0eefcd)
 	ignore:Unknown config option. consider_namespace_packages:pytest.PytestConfigWarning
+
+	# Ignore warnings we cannot do anything about:
+	# https://github.com/pypa/setuptools/pull/5042#issuecomment-2981138461
+	ignore:Couldn't import C tracer:coverage.exceptions.CoverageWarning