per page, with , order by , clip by
Results of 1 - 10 of about 142 for called (0.005 sec.)
How to use Django with Granian — Django 6.1 ドキュメント 12772
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » How to use Django with Granian ¶ Granian is a Rust-based high-performance HTTP server for Python applications, supporting ASGI and WSGI interfaces. ... o in Granian ¶ When Granian is installed, a granian command is available which runs ASGI applications. Granian needs to be called with the location of a module containing an ASGI application object, followed by what the application is called (separated ... 次のトピックへ Django を Hypercorn とともに使う 関連キーワード Granian granian application asgi applications install command called interface project How to Rust based high performance server supporting interfaces Installing Running installed available r ...
https://man.mtool.work/django/6.1/howto/deployment/asgi/granian.html
How to use Django with Granian — Django 6.1 ドキュメント 12546
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » How to use Django with Granian ¶ Granian is a Rust-based high-performance HTTP server for Python applications, supporting ASGI and WSGI interfaces. ... o in Granian ¶ When Granian is installed, a granian command is available which runs ASGI applications. Granian needs to be called with the location of a module containing an ASGI application object, followed by what the application is called (separated ... o を Hypercorn とともに使う 関連キーワード Granian Django granian application asgi Python applications install pip command called interface project your How to use Rust based high performance 関連するページ How to use Django with Granian How to release ...
https://man.mtool.work/django/6.1/howto/deployment/asgi/granian.html
How to use Django with Granian — Django 6.1 ドキュメント 10030
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » How to use Django with Granian ¶ Granian is a Rust-based high-performance HTTP server for Python applications, supporting ASGI and WSGI interfaces. ... o in Granian ¶ When Granian is installed, a granian command is available which runs WSGI applications. Granian needs to be called with the location of a module containing a WSGI application object named application , using the --interface wsgi option. ... project How to Rust based high performance server supporting interfaces Installing Running installed available runs needs called location クイック検索 Last update: 2026年10月09日 « previous | up | next » ...
https://man.mtool.work/django/6.1/howto/deployment/wsgi/granian.html
Django 1.7 リリースノート — Django 6.1 ドキュメント 8427
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.7 リリースノート ¶ September 2, 2014 Django 1.7 へようこそ! このリリースノートでは、 バージョン 1.7 の新機能 と、Django 1.6 以前からアップグ ... have slightly different arguments. Check the documentation for details. The allow_syncdb method on database routers is now called allow_migrate , but still performs the same function. Routers with allow_syncdb methods will still work, but that method n ... ermissions_mode parameters. See collectstatic for example usage. The CachedStaticFilesStorage backend gets a sibling class called ManifestStaticFilesStorage that doesn't use the cache system at all but instead a JSON file called staticfiles.json for st ... o digest time-zone-aware datetime instances performing the expected rendering. The cache tag will now try to use the cache called "template_fragments" if it exists and fall back to using the default cache otherwise. It also now accepts an optional usin ...
https://man.mtool.work/django/6.1/releases/1.7.html
Django 1.7 リリースノート — Django 6.1 ドキュメント 8427
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.7 リリースノート ¶ September 2, 2014 Django 1.7 へようこそ! このリリースノートでは、 バージョン 1.7 の新機能 と、Django 1.6 以前からアップグ ... have slightly different arguments. Check the documentation for details. The allow_syncdb method on database routers is now called allow_migrate , but still performs the same function. Routers with allow_syncdb methods will still work, but that method n ... ermissions_mode parameters. See collectstatic for example usage. The CachedStaticFilesStorage backend gets a sibling class called ManifestStaticFilesStorage that doesn't use the cache system at all but instead a JSON file called staticfiles.json for st ... o digest time-zone-aware datetime instances performing the expected rendering. The cache tag will now try to use the cache called "template_fragments" if it exists and fall back to using the default cache otherwise. It also now accepts an optional usin ...
https://man.mtool.work/django/6.1/releases/1.7.html
シグナル — Django 6.1 ドキュメント 7964
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » シグナル ¶ Django には "シグナルディスパッチャ" があり、フレームワークの他の場所でアクションが発生したときに、ほかのアプリケーションが通知を受けるの ... est_finished ) def my_receiver ( sender , ** kwargs ): print ( "Request finished!" ) Now, our my_receiver function will be called each time a request finishes. コードはどこに置くの? 厳密には、シグナル処理と登録のコードは好きな場所に置くことができますが ... s or asynchronous, receivers will be correctly adapted to whether send() or asend() is used. Synchronous receivers will be called using sync_to_async() when invoked via asend() . Asynchronous receivers will be called using async_to_sync() when invoked ... ng-style switches within a send() or asend() call, the receivers are grouped by whether or not they are async before being called. This means that an asynchronous receiver registered before a synchronous receiver may be executed after the synchronous r ...
https://man.mtool.work/django/6.1/topics/signals.html
シグナル — Django 6.1 ドキュメント 7964
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » シグナル ¶ Django には "シグナルディスパッチャ" があり、フレームワークの他の場所でアクションが発生したときに、ほかのアプリケーションが通知を受けるの ... est_finished ) def my_receiver ( sender , ** kwargs ): print ( "Request finished!" ) Now, our my_receiver function will be called each time a request finishes. コードはどこに置くの? 厳密には、シグナル処理と登録のコードは好きな場所に置くことができますが ... s or asynchronous, receivers will be correctly adapted to whether send() or asend() is used. Synchronous receivers will be called using sync_to_async() when invoked via asend() . Asynchronous receivers will be called using async_to_sync() when invoked ... ng-style switches within a send() or asend() call, the receivers are grouped by whether or not they are async before being called. This means that an asynchronous receiver registered before a synchronous receiver may be executed after the synchronous r ...
https://man.mtool.work/django/6.1/topics/signals.html
Django 1.3 リリースノート — Django 6.1 ドキュメント 7276
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.3 リリースノート ¶ March 23, 2011 Django 1.3 へようこそ! Nearly a year in the making, Django 1.3 includes quite a few new features and plen ... fferent models referencing the same file. In Django 1.3, when a model is deleted the FileField 's delete() method won't be called. If you need cleanup of orphaned files, you'll need to handle it yourself (for instance, with a custom management command ... performed in them; that is, either some model was saved, some bulk update or delete was performed, or the user explicitly called transaction.set_dirty() . In Django 1.3, a transaction is marked dirty when any database operation is performed. As a resu ... a GEOSException is properly raised to indicate possible faulty application code. A warning is now raised if transform() is called when the SRID of the geometry is less than 0 or None . CZBirthNumberField.clean ¶ Previously this field's clean() method a ...
https://man.mtool.work/django/6.1/releases/1.3.html
Django 1.3 リリースノート — Django 6.1 ドキュメント 7276
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.3 リリースノート ¶ March 23, 2011 Django 1.3 へようこそ! Nearly a year in the making, Django 1.3 includes quite a few new features and plen ... fferent models referencing the same file. In Django 1.3, when a model is deleted the FileField 's delete() method won't be called. If you need cleanup of orphaned files, you'll need to handle it yourself (for instance, with a custom management command ... performed in them; that is, either some model was saved, some bulk update or delete was performed, or the user explicitly called transaction.set_dirty() . In Django 1.3, a transaction is marked dirty when any database operation is performed. As a resu ... a GEOSException is properly raised to indicate possible faulty application code. A warning is now raised if transform() is called when the SRID of the geometry is less than 0 or None . CZBirthNumberField.clean ¶ Previously this field's clean() method a ...
https://man.mtool.work/django/6.1/releases/1.3.html
ミドルウェア (Middleware) — Django 6.1 ドキュメント 7276
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » ミドルウェア (Middleware) ¶ ミドルウェアは、Django のリクエスト/レスポンス処理にフックを加えるためのフレームワークです。これは、Django の入力あるいは ... alization. def middleware ( request ): # Code to be executed for each request before # the view (and later middleware) are called. response = get_response ( request ) # Code to be executed for each request/response after # the view is called. return re ... tion. def __call__ ( self , request ): # Code to be executed for each request before # the view (and later middleware) are called. response = self . get_response ( request ) # Code to be executed for each request/response after # the view is called. re ...
https://man.mtool.work/django/6.1/topics/http/middleware.html
PREV 1 2 3 4 5 6 7 8 9 10 NEXT