mirror of
https://github.com/django/django.git
synced 2025-08-03 18:38:50 +00:00
Fixed #25999 -- Removed promotion of RemovedInNextVersionWarning to loud by default.
This commit is contained in:
parent
28acc0d6df
commit
5b94b17fef
9 changed files with 5 additions and 116 deletions
|
@ -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
|
||||
|
|
|
@ -739,9 +739,6 @@ When :setting:`DEBUG` is ``True``:
|
|||
* The ``django`` catch-all logger sends all messages at the ``INFO`` level or
|
||||
higher to the console.
|
||||
|
||||
* The ``py.warnings`` logger, which handles messages from ``warnings.warn()``,
|
||||
sends messages to the console.
|
||||
|
||||
When :setting:`DEBUG` is ``False``:
|
||||
|
||||
* The ``django`` logger send messages with ``ERROR`` or ``CRITICAL`` level to
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue