From 4a03d348c70caa3e21393e08e6e665ef752202ac Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Sat, 17 Jan 2015 12:59:07 -0500 Subject: Removed BaseCommand.requires_model_validation per deprecation timeline. --- docs/howto/custom-management-commands.txt | 18 +----------------- 1 file changed, 1 insertion(+), 17 deletions(-) (limited to 'docs') diff --git a/docs/howto/custom-management-commands.txt b/docs/howto/custom-management-commands.txt index c55adb19fc..a87e0ef1ba 100644 --- a/docs/howto/custom-management-commands.txt +++ b/docs/howto/custom-management-commands.txt @@ -282,23 +282,7 @@ All attributes can be set in your derived class and can be used in .. versionadded:: 1.7 A boolean; if ``True``, the entire Django project will be checked for - potential problems prior to executing the command. If - ``requires_system_checks`` is missing, the value of - ``requires_model_validation`` is used. If the latter flag is missing - as well, the default value (``True``) is used. Defining both - ``requires_system_checks`` and ``requires_model_validation`` will result - in an error. - -.. attribute:: BaseCommand.requires_model_validation - -.. deprecated:: 1.7 - Replaced by ``requires_system_checks`` - - A boolean; if ``True``, validation of installed models will be - performed prior to executing the command. Default value is - ``True``. To validate an individual application's models - rather than all applications' models, call - :meth:`~BaseCommand.validate` from :meth:`~BaseCommand.handle`. + potential problems prior to executing the command. Default value is ``True``. .. attribute:: BaseCommand.leave_locale_alone -- cgit v1.3