diff options
| author | Tim Graham <timograham@gmail.com> | 2016-06-01 15:17:25 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2016-06-01 15:17:25 -0400 |
| commit | 3db04d4422326006519410715529f013faecad68 (patch) | |
| tree | 36458db3ade89fa05c16d279638eddcbc9ef2ad3 | |
| parent | af3273757397fa88163174546f2b620d7b4837ed (diff) | |
Fixed #26084 -- Documented that deprecation warnings are no longer loud.
| -rw-r--r-- | docs/releases/1.11.txt | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/docs/releases/1.11.txt b/docs/releases/1.11.txt index 3abb7db368..5a4f191912 100644 --- a/docs/releases/1.11.txt +++ b/docs/releases/1.11.txt @@ -27,6 +27,21 @@ recommend** and only officially support the latest release of each series. The Django 1.11.x series is the last to support Python 2. The next major release, Django 2.0, will only support Python 3.5+. +Deprecating warnings are no longer loud by default +================================================== + +Unlike older versions of Django, Django's own deprecation warnings are no +longer displayed by default. This is consistent with Python's default behavior. + +This change allows third-party apps to support both Django 1.11 LTS and Django +1.8 LTS without having to add code to avoid deprecation warnings. + +Following the release of Django 2.0, we suggest that third-party app authors +drop support for all versions of Django prior to 1.11. At that time, you should +be able run your package's tests using ``python -Wd`` so that deprecation +warnings do appear. After making the deprecation warning fixes, your app should +be compatible with Django 2.0. + What's new in Django 1.11 ========================= |