Ticket #22029: 22029.diff

File 22029.diff, 3.5 KB (added by Tim Graham, 11 years ago)

  • docs/ref/signals.txt 

    diff --git a/docs/ref/signals.txt b/docs/ref/signals.txt
index 7bdb188..4ed7987 100644
    a b pre_migrate  
    376376Sent by the :djadmin:`migrate` command before it starts to install an
    377377application. It's not emitted for applications that lack a ``models`` module.
    378378
    379 Any handlers that listen to this signal need to be written in a particular
    380 place: a ``management`` module in one of your :setting:`INSTALLED_APPS`. If
    381 handlers are registered anywhere else they may not be loaded by
    382 :djadmin:`migrate`.
     379Any handlers that listen to this signal need to be registered in a particular
     380place: the :meth:`AppConfig.ready() <django.apps.AppConfig.ready>` method within
     381the ``apps`` module in one of your :setting:`INSTALLED_APPS`. If handlers are
     382registered anywhere else they may not be loaded by :djadmin:`migrate`.
    383383
    384384Arguments sent with this signal:
    385385
    … … pre_syncdb  
    421421Sent by the :djadmin:`syncdb` command before it starts to install an
    422422application.
    423423
    424 Any handlers that listen to this signal need to be written in a particular
    425 place: a ``management`` module in one of your :setting:`INSTALLED_APPS`. If
    426 handlers are registered anywhere else they may not be loaded by
    427 :djadmin:`syncdb`.
     424Any handlers that listen to this signal need to be registered in a particular
     425place: the :meth:`AppConfig.ready() <django.apps.AppConfig.ready>` method within
     426the ``apps`` module in one of your :setting:`INSTALLED_APPS`. If handlers are
     427registered anywhere else they may not be loaded by :djadmin:`syncdb`.
    428428
    429429Arguments sent with this signal:
    430430
    … … Sent by the :djadmin:`migrate` command after it installs an application, and the  
    469469:djadmin:`flush` command. It's not emitted for applications that lack a
    470470``models`` module.
    471471
    472 Any handlers that listen to this signal need to be written in a particular
    473 place: a ``management`` module in one of your :setting:`INSTALLED_APPS`. If
    474 handlers are registered anywhere else they may not be loaded by
    475 :djadmin:`migrate`. It is important that handlers of this signal perform
    476 idempotent changes (e.g. no database alterations) as this may cause the
    477 :djadmin:`flush` management command to fail if it also ran during the
    478 :djadmin:`migrate` command.
     472Any handlers that listen to this signal need to be registered in a particular
     473place: the :meth:`AppConfig.ready() <django.apps.AppConfig.ready>` method within
     474the ``apps`` module in one of your :setting:`INSTALLED_APPS`. If handlers are
     475registered anywhere else they may not be loaded by :djadmin:`migrate`. It is
     476important that handlers of this signal perform idempotent changes (e.g. no
     477database alterations) as this may cause the :djadmin:`flush` management command
     478to fail if it also ran during the :djadmin:`migrate` command.
    479479
    480480Arguments sent with this signal:
    481481
    … … post_syncdb  
    529529Sent by the :djadmin:`syncdb` command after it installs an application, and the
    530530:djadmin:`flush` command.
    531531
    532 Any handlers that listen to this signal need to be written in a particular
    533 place: a ``management`` module in one of your :setting:`INSTALLED_APPS`. If
     532Any handlers that listen to this signal need to be registered in a particular
     533place: the :meth:`AppConfig.ready() <django.apps.AppConfig.ready>` method within
     534the ``apps`` module in one of your :setting:`INSTALLED_APPS`. If
    534535handlers are registered anywhere else they may not be loaded by
    535536:djadmin:`syncdb`. It is important that handlers of this signal perform
    536537idempotent changes (e.g. no database alterations) as this may cause the
Back to Top