per page, with , order by , clip by
Results of 1 - 10 of about 58 for Signal (0.007 sec.)
シグナル — Django 6.1 ドキュメント 14842
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » シグナル ¶ Django には "シグナルディスパッチャ" があり、フレームワークの他の場所でアクションが発生したときに、ほかのアプリケーションが通知を受けるの ... 、サードパーティのアプリを登録して、設定変更の通知を受けることができます: from django.apps import AppConfig from django.core.signals import setting_changed def my_receiver ( sender , ** kwargs ): print ( "Setting changed!" ) class MyAppConfig ( AppConfig ... ルでディスパッチするのではなく、処理コードを直接呼び出すことを選ぶべきです。 シグナルを待ち受ける ¶ シグナルを受信するには、 Signal.connect() メソッドを使って receiver 関数を登録します。シグナルが送信されると、レシーバ関数が呼び出されます。シグナルのすべ ... てのレシーバ関数は、登録された順番に1つずつ呼び出されます。 Signal. connect ( receiver , sender = None , weak = True , dispatch_uid = None ) [ソース] ¶ パラメータ : receiver -- このシグナル ...
https://man.mtool.work/django/6.1/topics/signals.html
シグナル — Django 6.1 ドキュメント 14842
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » シグナル ¶ Django には "シグナルディスパッチャ" があり、フレームワークの他の場所でアクションが発生したときに、ほかのアプリケーションが通知を受けるの ... 、サードパーティのアプリを登録して、設定変更の通知を受けることができます: from django.apps import AppConfig from django.core.signals import setting_changed def my_receiver ( sender , ** kwargs ): print ( "Setting changed!" ) class MyAppConfig ( AppConfig ... ルでディスパッチするのではなく、処理コードを直接呼び出すことを選ぶべきです。 シグナルを待ち受ける ¶ シグナルを受信するには、 Signal.connect() メソッドを使って receiver 関数を登録します。シグナルが送信されると、レシーバ関数が呼び出されます。シグナルのすべ ... てのレシーバ関数は、登録された順番に1つずつ呼び出されます。 Signal. connect ( receiver , sender = None , weak = True , dispatch_uid = None ) [ソース] ¶ パラメータ : receiver -- このシグナル ...
https://man.mtool.work/django/6.1/topics/signals.html
Django 1.5 リリースノート — Django 6.1 ドキュメント 8226
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.5 リリースノート ¶ February 26, 2013 Django 1.5 へようこそ! These release notes cover the new features , as well as some backwards incompat ... the acceptable codes for Quebec. It's an old abbreviation. The receiver decorator is now able to connect to more than one signal by supplying a list of signals. In the admin, you can now filter users by groups which they are members of. QuerySet.bulk_ ... practice to provide those templates in order to present pretty error pages to the user. django.contrib.auth provides a new signal that is emitted whenever a user fails to login successfully. See user_login_failed The new loaddata --ignorenonexistent op ... opers wishing to access the raw POST data for these cases, should use the request.body attribute instead. request_finished signal ¶ Django used to send the request_finished signal as soon as the view function returned a response. This interacted badly ...
https://man.mtool.work/django/6.1/releases/1.5.html
Django 1.5 リリースノート — Django 6.1 ドキュメント 8226
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.5 リリースノート ¶ February 26, 2013 Django 1.5 へようこそ! These release notes cover the new features , as well as some backwards incompat ... the acceptable codes for Quebec. It's an old abbreviation. The receiver decorator is now able to connect to more than one signal by supplying a list of signals. In the admin, you can now filter users by groups which they are members of. QuerySet.bulk_ ... practice to provide those templates in order to present pretty error pages to the user. django.contrib.auth provides a new signal that is emitted whenever a user fails to login successfully. See user_login_failed The new loaddata --ignorenonexistent op ... opers wishing to access the raw POST data for these cases, should use the request.body attribute instead. request_finished signal ¶ Django used to send the request_finished signal as soon as the view function returned a response. This interacted badly ...
https://man.mtool.work/django/6.1/releases/1.5.html
フィクスチャ (fixture) — Django 6.1 ドキュメント 8167
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » フィクスチャ (fixture) ¶ フィクスチャ (fixture) とは、シリアライズされたデータベースのコンテンツを含むファイルのコレクションです。各フィクスチャには ... is saved to the database as is. Model defined save() methods are not called, and any pre_save , post_save , or m2m_changed signals will be called with raw=True since the instance only contains attributes that are local to the model. You may, for exampl ... ss related fields that aren't present during fixture loading and would otherwise raise an exception: from django.db.models.signals import post_save from .models import MyModel def my_handler ( ** kwargs ): # disable the handler during fixture loading i ... Model ) このロジックをカプセル化するデコレータを書くこともできます: from functools import wraps def disable_for_loaddata ( signal_handler ): """ Decorator that turns off signal handlers when loading fixture data. """ @wraps ( signal_handler ) def wrapp ...
https://man.mtool.work/django/6.1/topics/db/fixtures.html
フィクスチャ (fixture) — Django 6.1 ドキュメント 7845
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » フィクスチャ (fixture) ¶ フィクスチャ (fixture) とは、シリアライズされたデータベースのコンテンツを含むファイルのコレクションです。各フィクスチャには ... is saved to the database as is. Model defined save() methods are not called, and any pre_save , post_save , or m2m_changed signals will be called with raw=True since the instance only contains attributes that are local to the model. You may, for exampl ... ss related fields that aren't present during fixture loading and would otherwise raise an exception: from django.db.models.signals import post_save from .models import MyModel def my_handler ( ** kwargs ): # disable the handler during fixture loading i ... Model ) このロジックをカプセル化するデコレータを書くこともできます: from functools import wraps def disable_for_loaddata ( signal_handler ): """ Decorator that turns off signal handlers when loading fixture data. """ @wraps ( signal_handler ) def wrapp ...
https://man.mtool.work/django/6.1/topics/db/fixtures.html
Porting your apps from Django 0.96 to 1.0 — Django 6.1 ドキュメント 7464
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Porting your apps from Django 0.96 to 1.0 ¶ Django 1.0 breaks compatibility with 0.96 in some areas. This guide will help you port 0.96 projects and ... probably worth reading through the list and checking your code for these things. シグナル ¶ Add **kwargs to any registered signal handlers. Connect, disconnect, and send signals via methods on the Signal object instead of through module methods in djan ... .dispatch.dispatcher . Remove any use of the Anonymous and Any sender options; they no longer exist. You can still receive signals sent by any sender by using sender=None Make any custom signals you've declared into instances of django.dispatch.Signal ... eed to make: Old (0.96) New (1.0) def callback(sender) def callback(sender, **kwargs) sig = object() sig = django.dispatch.Signal() dispatcher.connect(callback, sig) sig.connect(callback) dispatcher.send(sig, sender) sig.send(sender) dispatcher.connect ...
https://man.mtool.work/django/6.1/releases/1.0-porting-guide.html
Porting your apps from Django 0.96 to 1.0 — Django 6.1 ドキュメント 7464
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Porting your apps from Django 0.96 to 1.0 ¶ Django 1.0 breaks compatibility with 0.96 in some areas. This guide will help you port 0.96 projects and ... probably worth reading through the list and checking your code for these things. シグナル ¶ Add **kwargs to any registered signal handlers. Connect, disconnect, and send signals via methods on the Signal object instead of through module methods in djan ... .dispatch.dispatcher . Remove any use of the Anonymous and Any sender options; they no longer exist. You can still receive signals sent by any sender by using sender=None Make any custom signals you've declared into instances of django.dispatch.Signal ... eed to make: Old (0.96) New (1.0) def callback(sender) def callback(sender, **kwargs) sig = object() sig = django.dispatch.Signal() dispatcher.connect(callback, sig) sig.connect(callback) dispatcher.send(sig, sender) sig.send(sender) dispatcher.connect ...
https://man.mtool.work/django/6.1/releases/1.0-porting-guide.html
Django 1.8 リリースノート — Django 6.1 ドキュメント 7274
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.8 リリースノート ¶ April 1, 2015 Django 1.8 へようこそ! このリリースノートでは、 バージョン 1.8 の新機能 と、Django 1.7 以前からアップグレー ... ow used when primary key field's are set to None . シグナル ¶ Exceptions from the (receiver, exception) tuples returned by Signal.send_robust() now have their traceback attached as a __traceback__ attribute. The environ argument, which contains the WSG ... I environment structure from the request, was added to the request_started signal. You can now import the setting_changed() signal from django.core.signals to avoid loading django.test in non-test situati ... from within a transaction, provided your database supports transactions. This has one backwards incompatible side effect, signal handlers triggered from these methods are now executed within the method's transaction and any exception in a signal handl ...
https://man.mtool.work/django/6.1/releases/1.8.html
Django 1.8 リリースノート — Django 6.1 ドキュメント 7274
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.8 リリースノート ¶ April 1, 2015 Django 1.8 へようこそ! このリリースノートでは、 バージョン 1.8 の新機能 と、Django 1.7 以前からアップグレー ... ow used when primary key field's are set to None . シグナル ¶ Exceptions from the (receiver, exception) tuples returned by Signal.send_robust() now have their traceback attached as a __traceback__ attribute. The environ argument, which contains the WSG ... I environment structure from the request, was added to the request_started signal. You can now import the setting_changed() signal from django.core.signals to avoid loading django.test in non-test situati ... from within a transaction, provided your database supports transactions. This has one backwards incompatible side effect, signal handlers triggered from these methods are now executed within the method's transaction and any exception in a signal handl ...
https://man.mtool.work/django/6.1/releases/1.8.html
PREV 1 2 3 4 5 6 NEXT