Fixed #17997 - Documented that the debug server is now multithreaded by default.

Thanks trey.smith@ for the report and vanessagomes for the patch.
This commit is contained in:
Tim Graham 2012-07-05 08:39:05 -04:00
parent a222d6e800
commit e4a1407a9c
2 changed files with 10 additions and 1 deletions

View File

@ -668,6 +668,7 @@ Example usage::
.. versionadded:: 1.4 .. versionadded:: 1.4
Since version 1.4, the development server is multithreaded by default.
Use the ``--nothreading`` option to disable the use of threading in the Use the ``--nothreading`` option to disable the use of threading in the
development server. development server.

View File

@ -1145,6 +1145,15 @@ field. This was something that should not have worked, and in 1.4 loading such
incomplete fixtures will fail. Because fixtures are a raw import, they should incomplete fixtures will fail. Because fixtures are a raw import, they should
explicitly specify all field values, regardless of field options on the model. explicitly specify all field values, regardless of field options on the model.
Development Server Multithreading
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The development server is now is multithreaded by default. Use the
:djadminopt:`--nothreading` option to disable the use of threading in the
development server::
django-admin.py runserver --nothreading
Attributes disabled in markdown when safe mode set Attributes disabled in markdown when safe mode set
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@ -1338,4 +1347,3 @@ Versions of Python-Markdown earlier than 2.1 do not support the option to
disable attributes. As a security issue, earlier versions of this library will disable attributes. As a security issue, earlier versions of this library will
not be supported by the markup contrib app in 1.5 under an accelerated not be supported by the markup contrib app in 1.5 under an accelerated
deprecation timeline. deprecation timeline.