diff options
| author | Tim Graham <timograham@gmail.com> | 2016-01-13 19:02:39 -0500 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2016-01-14 09:05:43 -0500 |
| commit | 5b94b17feff15a9f0345f92fc0568bfe7038e3a3 (patch) | |
| tree | c1dba0a0e0a3eba2ed687e04187dc4b70cae10a6 /docs/internals | |
| parent | 28acc0d6df844ccfc8de6f4e7d5883eb4841e946 (diff) | |
Fixed #25999 -- Removed promotion of RemovedInNextVersionWarning to loud by default.
Diffstat (limited to 'docs/internals')
| -rw-r--r-- | docs/internals/release-process.txt | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/internals/release-process.txt b/docs/internals/release-process.txt index 7ca2e452a5..2c05f909d9 100644 --- a/docs/internals/release-process.txt +++ b/docs/internals/release-process.txt @@ -92,16 +92,16 @@ So, for example, if we decided to start the deprecation of a function in Django 4.2: * Django 4.2 will contain a backwards-compatible replica of the function which - will raise a ``RemovedInDjango51Warning``. This warning is silent by - default; you can turn on display of these warnings with the ``-Wd`` option - of Python. + will raise a ``RemovedInDjango51Warning``. * Django 5.0 (the version that follows 4.2) will still contain the - backwards-compatible replica. This warning becomes *loud* by default and - will likely be quite annoying. + backwards-compatible replica. * Django 5.1 will remove the feature outright. +The warnings are silent by default. You can turn on display of these warnings +with the ``python -Wd`` option. + A more generic example: * X.0 |