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