innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Rewrote 'Test with warnings enabled' section of docs/topics/testing.txt from [14019] to be clearer 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@14033 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty 2010-10-08 20:30:02 +00:00
parent bca8aed419
commit 40777cb533
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/topics/testing.txt
View File

@ -311,11 +311,11 @@ be reported, and any test databases created by the run will not be destroyed.
.. admonition:: Test with warnings enabled .. admonition:: Test with warnings enabled
It is a good idea to run your tests with ``python -Wall manage.py It's a good idea to run your tests with Python warnings enabled:
test``. This will allow you to catch any deprecation warnings that ``python -Wall manage.py test``. The ``-Wall`` flag tells Python to
might be in your code. Django (as well as many other libraries) use display deprecation warnings. Django, like many other Python libraries,
warnings to flag when features are deprecated. It can also flag uses these warnings to flag when features are going away. It also might
areas in your code that are not strictly wrong, but may benefit flag areas in your code that aren't strictly wrong but could benefit
from a better implementation. from a better implementation.
Running tests outside the test runner Running tests outside the test runner