per page, with , order by , clip by
Results of 1 - 10 of about 32 for connect (0.002 sec.)
シグナル — Django 6.1 ドキュメント 12372
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » シグナル ¶ Django には "シグナルディスパッチャ" があり、フレームワークの他の場所でアクションが発生したときに、ほかのアプリケーションが通知を受けるの ... der , ** kwargs ): print ( "Setting changed!" ) class MyAppConfig ( AppConfig ): ... def ready ( self ): setting_changed . connect ( my_receiver ) Django の 組み込みのシグナル は、ユーザコードに特定のアクションを通知します。 また、独自のカスタムシグナル ... スパッチするのではなく、処理コードを直接呼び出すことを選ぶべきです。 シグナルを待ち受ける ¶ シグナルを受信するには、 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 ドキュメント 12291
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » シグナル ¶ Django には "シグナルディスパッチャ" があり、フレームワークの他の場所でアクションが発生したときに、ほかのアプリケーションが通知を受けるの ... der , ** kwargs ): print ( "Setting changed!" ) class MyAppConfig ( AppConfig ): ... def ready ( self ): setting_changed . connect ( my_receiver ) Django の 組み込みのシグナル は、ユーザコードに特定のアクションを通知します。 また、独自のカスタムシグナル ... スパッチするのではなく、処理コードを直接呼び出すことを選ぶべきです。 シグナルを待ち受ける ¶ シグナルを受信するには、 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.8.16 リリースノート — Django 6.1 ドキュメント 10326
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.8.16 リリースノート ¶ November 1, 2016 Django 1.8.16 fixes two security issues in 1.8.15. User with hardcoded password created when running ... TEST dictionary, a hardcoded password is used. This could allow an attacker with network access to the database server to connect. This user is usually dropped after the test suite completes, but not when using the manage.py test --keepdb option or if ... the user has an active session (such as an attacker's connection). A randomly generated password is now used for each test run. DNS rebinding vulnerability when DEBUG=True ¶ Older vers ... site scripting vector, which could be quite serious if developers load a copy of the production database in development or connect to some production services for which there's no development instance, for example. If a project uses a package like the d ...
https://man.mtool.work/django/6.1/releases/1.8.16.html
Django 1.9.11 リリースノート — Django 6.1 ドキュメント 10229
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.9.11 リリースノート ¶ November 1, 2016 Django 1.9.11 では、1.9.10 にあった2つのセキュリティの問題を修正しました。 User with hardcoded passw ... TEST dictionary, a hardcoded password is used. This could allow an attacker with network access to the database server to connect. This user is usually dropped after the test suite completes, but not when using the manage.py test --keepdb option or if ... the user has an active session (such as an attacker's connection). A randomly generated password is now used for each test run. DNS rebinding vulnerability when DEBUG=True ¶ Older vers ... site scripting vector, which could be quite serious if developers load a copy of the production database in development or connect to some production services for which there's no development instance, for example. If a project uses a package like the d ...
https://man.mtool.work/django/6.1/releases/1.9.11.html
Django 1.8.16 リリースノート — Django 6.1 ドキュメント 10149
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.8.16 リリースノート ¶ November 1, 2016 Django 1.8.16 fixes two security issues in 1.8.15. User with hardcoded password created when running ... TEST dictionary, a hardcoded password is used. This could allow an attacker with network access to the database server to connect. This user is usually dropped after the test suite completes, but not when using the manage.py test --keepdb option or if ... the user has an active session (such as an attacker's connection). A randomly generated password is now used for each test run. DNS rebinding vulnerability when DEBUG=True ¶ Older vers ... site scripting vector, which could be quite serious if developers load a copy of the production database in development or connect to some production services for which there's no development instance, for example. If a project uses a package like the d ...
https://man.mtool.work/django/6.1/releases/1.8.16.html
Django 1.9.11 リリースノート — Django 6.1 ドキュメント 10052
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.9.11 リリースノート ¶ November 1, 2016 Django 1.9.11 では、1.9.10 にあった2つのセキュリティの問題を修正しました。 User with hardcoded passw ... TEST dictionary, a hardcoded password is used. This could allow an attacker with network access to the database server to connect. This user is usually dropped after the test suite completes, but not when using the manage.py test --keepdb option or if ... the user has an active session (such as an attacker's connection). A randomly generated password is now used for each test run. DNS rebinding vulnerability when DEBUG=True ¶ Older vers ... site scripting vector, which could be quite serious if developers load a copy of the production database in development or connect to some production services for which there's no development instance, for example. If a project uses a package like the d ...
https://man.mtool.work/django/6.1/releases/1.9.11.html
Django 1.10.3 リリースノート — Django 6.1 ドキュメント 9875
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.10.3 リリースノート ¶ November 1, 2016 Django 1.10.3 fixes two security issues and several bugs in 1.10.2. User with hardcoded password cre ... TEST dictionary, a hardcoded password is used. This could allow an attacker with network access to the database server to connect. This user is usually dropped after the test suite completes, but not when using the manage.py test --keepdb option or if ... the user has an active session (such as an attacker's connection). A randomly generated password is now used for each test run. DNS rebinding vulnerability when DEBUG=True ¶ Older vers ... site scripting vector, which could be quite serious if developers load a copy of the production database in development or connect to some production services for which there's no development instance, for example. If a project uses a package like the d ...
https://man.mtool.work/django/6.1/releases/1.10.3.html
Django 1.10.3 リリースノート — Django 6.1 ドキュメント 9794
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.10.3 リリースノート ¶ November 1, 2016 Django 1.10.3 fixes two security issues and several bugs in 1.10.2. User with hardcoded password cre ... TEST dictionary, a hardcoded password is used. This could allow an attacker with network access to the database server to connect. This user is usually dropped after the test suite completes, but not when using the manage.py test --keepdb option or if ... the user has an active session (such as an attacker's connection). A randomly generated password is now used for each test run. DNS rebinding vulnerability when DEBUG=True ¶ Older vers ... site scripting vector, which could be quite serious if developers load a copy of the production database in development or connect to some production services for which there's no development instance, for example. If a project uses a package like the d ...
https://man.mtool.work/django/6.1/releases/1.10.3.html
Porting your apps from Django 0.96 to 1.0 — Django 6.1 ドキュメント 8264
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 ... ading 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 django.dispatch.dispat ... 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(callback, sig, sende ... r=Any) sig.connect(callback, sender=None) コメント ¶ If you were using Django 0.96's django.contrib.comments app, you'll need to upgrade to t ...
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 ドキュメント 8183
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 ... ading 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 django.dispatch.dispat ... 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(callback, sig, sende ... r=Any) sig.connect(callback, sender=None) コメント ¶ If you were using Django 0.96's django.contrib.comments app, you'll need to upgrade to t ...
https://man.mtool.work/django/6.1/releases/1.0-porting-guide.html
PREV 1 2 3 4 NEXT