per page, with , order by , clip by
Results of 1 - 10 of about 16 for supporting (0.004 sec.)
How to use Django with Granian — Django 6.1 ドキュメント 12788
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. ... n granian application asgi applications install command called interface project How to Rust based high performance server supporting interfaces Installing Running installed available runs needs location クイック検索 Last update: 2026年10月09日 « previous ...
https://man.mtool.work/django/6.1/howto/deployment/asgi/granian.html
How to use Django with Granian — Django 6.1 ドキュメント 12788
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. ... Granian granian application wsgi applications install command interface project How to Rust based high performance server supporting interfaces Installing Running installed available runs needs called location クイック検索 Last update: 2026年10月09日 « pr ...
https://man.mtool.work/django/6.1/howto/deployment/wsgi/granian.html
How to use Django with Granian — Django 6.1 ドキュメント 9513
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. ...
https://man.mtool.work/django/6.1/howto/deployment/asgi/granian.html
How to use Django with Granian — Django 6.1 ドキュメント 9513
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. ...
https://man.mtool.work/django/6.1/howto/deployment/wsgi/granian.html
Migrating email to mailers — Django 6.1 ドキュメント 8750
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Migrating email to mailers ¶ Django 6.1 introduced the MAILERS setting, replacing EMAIL_BACKEND and several other EMAIL_* settings. It also introduc ... lf.alias is None . (Django's built-in backends check this to decide whether deprecated settings should be used.) Libraries supporting older Django versions will need to use getattr(self, "alias", None) . Backends that borrow Django's SMTP email settings li ... in use ( self.alias is not None ), as this will cause a "not available when MAILERS is defined" AttributeError . Libraries supporting multiple Django versions can identify support for mailers with either hasattr(django.core.mail, "mailers") or django.VERSI ...
https://man.mtool.work/django/6.1/howto/mailers-migration.html
Migrating email to mailers — Django 6.1 ドキュメント 8750
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Migrating email to mailers ¶ Django 6.1 introduced the MAILERS setting, replacing EMAIL_BACKEND and several other EMAIL_* settings. It also introduc ... lf.alias is None . (Django's built-in backends check this to decide whether deprecated settings should be used.) Libraries supporting older Django versions will need to use getattr(self, "alias", None) . Backends that borrow Django's SMTP email settings li ... in use ( self.alias is not None ), as this will cause a "not available when MAILERS is defined" AttributeError . Libraries supporting multiple Django versions can identify support for mailers with either hasattr(django.core.mail, "mailers") or django.VERSI ...
https://man.mtool.work/django/6.1/howto/mailers-migration.html
アクセシビリティ — Django 6.1 ドキュメント 8491
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » アクセシビリティ ¶ The Django project is committed to ensuring that websites built with Django are usable by everyone, including people with disabil ... in interface and default form rendering, should adhere to established accessibility standards and meet our own targets for supporting specific input devices and assistive technologies. アクセシビリティ基準 ¶ We work to conform with the Web Content Accessib ...
https://man.mtool.work/django/6.1/internals/contributing/accessibility.html
アクセシビリティ — Django 6.1 ドキュメント 8491
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » アクセシビリティ ¶ The Django project is committed to ensuring that websites built with Django are usable by everyone, including people with disabil ... in interface and default form rendering, should adhere to established accessibility standards and meet our own targets for supporting specific input devices and assistive technologies. アクセシビリティ基準 ¶ We work to conform with the Web Content Accessib ...
https://man.mtool.work/django/6.1/internals/contributing/accessibility.html
クエリを作成する — Django 6.1 ドキュメント 7745
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » クエリを作成する ¶ 一度 データモデル を作成すれば、Django はデータオブジェクトの作成、取得、更新および削除を行えるようにデータベースを抽象化した API ... log . objects . create ( name = "Batucada Blog" ) >>> e = Entry . objects . create ( ... blog = batucada , ... headline = "Supporting social movements with drums" , ... pub_date = date ( 2019 , 6 , 14 ), ... ) >>> gloria = Author . objects . create ( name ... d thus a more permissive filter: >>> anna . entry_set . filter () . filter ( authors__name = "Gloria" ) <QuerySet [<Entry: Supporting social movements with drums>]> exclude() is also sticky Please note that for this example, exclude() behaves similarly to ... ntry e despite being co-authored by Gloria: >>> anna . entry_set . exclude ( authors__name = "Gloria" ) <QuerySet [<Entry: Supporting social movements with drums>]> When chaining a second exclude() call, an empty QuerySet is returned, as expected: >>> anna ...
https://man.mtool.work/django/6.1/topics/db/queries.html
クエリを作成する — Django 6.1 ドキュメント 7745
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » クエリを作成する ¶ 一度 データモデル を作成すれば、Django はデータオブジェクトの作成、取得、更新および削除を行えるようにデータベースを抽象化した API ... log . objects . create ( name = "Batucada Blog" ) >>> e = Entry . objects . create ( ... blog = batucada , ... headline = "Supporting social movements with drums" , ... pub_date = date ( 2019 , 6 , 14 ), ... ) >>> gloria = Author . objects . create ( name ... d thus a more permissive filter: >>> anna . entry_set . filter () . filter ( authors__name = "Gloria" ) <QuerySet [<Entry: Supporting social movements with drums>]> exclude() is also sticky Please note that for this example, exclude() behaves similarly to ... ntry e despite being co-authored by Gloria: >>> anna . entry_set . exclude ( authors__name = "Gloria" ) <QuerySet [<Entry: Supporting social movements with drums>]> When chaining a second exclude() call, an empty QuerySet is returned, as expected: >>> anna ...
https://man.mtool.work/django/6.1/topics/db/queries.html
PREV 1 2 NEXT