From fbb93581498070272dd67c6e0afbca13cb89d5f3 Mon Sep 17 00:00:00 2001 From: Daniel Chimeno Date: Wed, 28 Mar 2018 19:25:03 +0200 Subject: Replaced 'python -Wall' with 'python -Wa'. --- docs/internals/contributing/writing-code/submitting-patches.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/internals/contributing/writing-code') diff --git a/docs/internals/contributing/writing-code/submitting-patches.txt b/docs/internals/contributing/writing-code/submitting-patches.txt index cbda36075d..15dd431229 100644 --- a/docs/internals/contributing/writing-code/submitting-patches.txt +++ b/docs/internals/contributing/writing-code/submitting-patches.txt @@ -175,7 +175,7 @@ the first release of Django that deprecates a feature (``A.B``) should raise a will be removed) when the deprecated feature is invoked. Assuming we have good test coverage, these warnings are converted to errors when :ref:`running the test suite ` with warnings enabled: -``python -Wall runtests.py``. Thus, when adding a ``RemovedInDjangoXXWarning`` +``python -Wa runtests.py``. Thus, when adding a ``RemovedInDjangoXXWarning`` you need to eliminate or silence any warnings generated when running the tests. The first step is to remove any use of the deprecated behavior by Django itself. -- cgit v1.3