per page, with , order by , clip by
Results of 1 - 10 of about 112 for third (0.004 sec.)
Migrating email to mailers — Django 6.1 ドキュメント 10871
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 ... on migrating existing projects to the new mailers functionality. All Django projects that send email should: If using any third-party packages that send email, verify their compatibility with MAILERS before making other changes. Update email-related ... ning with deprecation warnings enabled in production to catch those deprecations. Or carefully review your code (including third-party packages) for use of any deprecated email features. Other updates are needed only for projects or reusable Django li ... "timeout" in "OPTIONS" . EMAIL_USE_SSL becomes "use_ssl" in "OPTIONS" . EMAIL_USE_TLS becomes "use_tls" in "OPTIONS" . For third-party or custom email backends, the available "OPTIONS" depend on the backend. Refer to the third-party documentation, or ...
https://man.mtool.work/django/6.1/howto/mailers-migration.html
Migrating email to mailers — Django 6.1 ドキュメント 10871
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 ... on migrating existing projects to the new mailers functionality. All Django projects that send email should: If using any third-party packages that send email, verify their compatibility with MAILERS before making other changes. Update email-related ... ning with deprecation warnings enabled in production to catch those deprecations. Or carefully review your code (including third-party packages) for use of any deprecated email features. Other updates are needed only for projects or reusable Django li ... "timeout" in "OPTIONS" . EMAIL_USE_SSL becomes "use_ssl" in "OPTIONS" . EMAIL_USE_TLS becomes "use_tls" in "OPTIONS" . For third-party or custom email backends, the available "OPTIONS" depend on the backend. Refer to the third-party documentation, or ...
https://man.mtool.work/django/6.1/howto/mailers-migration.html
Django 1.3.5 リリースノート — Django 6.1 ドキュメント 10037
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.3.5 リリースノート ¶ December 10, 2012 Django 1.3.5 addresses two security issues present in previous Django releases in the 1.3 series. Pl ... itional validation of the scheme of the URL to redirect to (since, both within Django's own supplied applications and many third-party applications, accepting a user-supplied redirect target is a common pattern). Since then, two independent audits of ... the Host-header issue, we are taking steps to provide tighter validation in response to reported problems (primarily with third-party applications, but to a certain extent also within Django itself). This comes in two parts: 1. A new utility function ... ended for use whenever user-supplied redirect targets are accepted, to ensure that such redirects cannot lead to arbitrary third-party sites. 2. All of Django's own built-in views -- primarily in the authentication system -- which allow user-supplied ...
https://man.mtool.work/django/6.1/releases/1.3.5.html
Django 1.4.3 リリースノート — Django 6.1 ドキュメント 10037
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.4.3 リリースノート ¶ December 10, 2012 Django 1.4.3 addresses two security issues present in previous Django releases in the 1.4 series. Pl ... itional validation of the scheme of the URL to redirect to (since, both within Django's own supplied applications and many third-party applications, accepting a user-supplied redirect target is a common pattern). Since then, two independent audits of ... the Host-header issue, we are taking steps to provide tighter validation in response to reported problems (primarily with third-party applications, but to a certain extent also within Django itself). This comes in two parts: 1. A new utility function ... ended for use whenever user-supplied redirect targets are accepted, to ensure that such redirects cannot lead to arbitrary third-party sites. 2. All of Django's own built-in views -- primarily in the authentication system -- which allow user-supplied ...
https://man.mtool.work/django/6.1/releases/1.4.3.html
Django 1.3.5 リリースノート — Django 6.1 ドキュメント 9759
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.3.5 リリースノート ¶ December 10, 2012 Django 1.3.5 addresses two security issues present in previous Django releases in the 1.3 series. Pl ... itional validation of the scheme of the URL to redirect to (since, both within Django's own supplied applications and many third-party applications, accepting a user-supplied redirect target is a common pattern). Since then, two independent audits of ... the Host-header issue, we are taking steps to provide tighter validation in response to reported problems (primarily with third-party applications, but to a certain extent also within Django itself). This comes in two parts: 1. A new utility function ... ended for use whenever user-supplied redirect targets are accepted, to ensure that such redirects cannot lead to arbitrary third-party sites. 2. All of Django's own built-in views -- primarily in the authentication system -- which allow user-supplied ...
https://man.mtool.work/django/6.1/releases/1.3.5.html
Django 1.4.3 リリースノート — Django 6.1 ドキュメント 9759
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.4.3 リリースノート ¶ December 10, 2012 Django 1.4.3 addresses two security issues present in previous Django releases in the 1.4 series. Pl ... itional validation of the scheme of the URL to redirect to (since, both within Django's own supplied applications and many third-party applications, accepting a user-supplied redirect target is a common pattern). Since then, two independent audits of ... the Host-header issue, we are taking steps to provide tighter validation in response to reported problems (primarily with third-party applications, but to a certain extent also within Django itself). This comes in two parts: 1. A new utility function ... ended for use whenever user-supplied redirect targets are accepted, to ensure that such redirects cannot lead to arbitrary third-party sites. 2. All of Django's own built-in views -- primarily in the authentication system -- which allow user-supplied ...
https://man.mtool.work/django/6.1/releases/1.4.3.html
Django 2.2 リリースノート — Django 6.1 ドキュメント 9468
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 2.2 リリースノート ¶ April 1, 2019 Django 2.2 へようこそ! このリリースノートでは、 バージョン 2.2 の新機能 と、Django 2.1 以前からアップグレー ... クエンド API ¶ このセクションでは、サードパーティのデータベースバックエンドで必要になる可能性のある変更について説明します。 Third-party database backends must implement support for table check constraints or set DatabaseFeatures.supports_table_check_co ... nstraints to False . Third party database backends must implement support for ignoring constraints or uniqueness errors while inserting or set Databa ... seFeatures.supports_ignore_conflicts to False . Third party database backends must implement introspection for DurationField or set DatabaseFeatures.can_introspect_duration_fie ...
https://man.mtool.work/django/6.1/releases/2.2.html
Django 2.2 リリースノート — Django 6.1 ドキュメント 9468
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 2.2 リリースノート ¶ April 1, 2019 Django 2.2 へようこそ! このリリースノートでは、 バージョン 2.2 の新機能 と、Django 2.1 以前からアップグレー ... クエンド API ¶ このセクションでは、サードパーティのデータベースバックエンドで必要になる可能性のある変更について説明します。 Third-party database backends must implement support for table check constraints or set DatabaseFeatures.supports_table_check_co ... nstraints to False . Third party database backends must implement support for ignoring constraints or uniqueness errors while inserting or set Databa ... seFeatures.supports_ignore_conflicts to False . Third party database backends must implement introspection for DurationField or set DatabaseFeatures.can_introspect_duration_fie ...
https://man.mtool.work/django/6.1/releases/2.2.html
メールを送信する — Django 6.1 ドキュメント 8495
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » メールを送信する ¶ Django provides wrappers for Python's email and smtplib modules to simplify composing and sending email. Django's email framework ... ions, including SMTP servers in your own infrastructure and most commercial email service providers (ESPs). There are also third-party email backends available that integrate directly with ESP APIs or add other sending features. During development or ... iron [ "EMAIL_ACCOUNT_ID" ], "password" : os . environ [ "EMAIL_API_KEY" ], }, }, "notifications" : { "BACKEND" : "example.third.party.EmailBackend" , "OPTIONS" : { "api_key" : os . environ [ "THIRD_PARTY_API_KEY" ], "region" : "eu" , }, }, "admin" : ... e variation of this authentication scheme.) "notifications" sends through a hypothetical commercial email service, using a third-party EmailBackend that connects directly to their API. (See Third-party backends for pointers on locating real, community ...
https://man.mtool.work/django/6.1/topics/email.html
メールを送信する — Django 6.1 ドキュメント 8495
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » メールを送信する ¶ Django provides wrappers for Python's email and smtplib modules to simplify composing and sending email. Django's email framework ... ions, including SMTP servers in your own infrastructure and most commercial email service providers (ESPs). There are also third-party email backends available that integrate directly with ESP APIs or add other sending features. During development or ... iron [ "EMAIL_ACCOUNT_ID" ], "password" : os . environ [ "EMAIL_API_KEY" ], }, }, "notifications" : { "BACKEND" : "example.third.party.EmailBackend" , "OPTIONS" : { "api_key" : os . environ [ "THIRD_PARTY_API_KEY" ], "region" : "eu" , }, }, "admin" : ... e variation of this authentication scheme.) "notifications" sends through a hypothetical commercial email service, using a third-party EmailBackend that connects directly to their API. (See Third-party backends for pointers on locating real, community ...
https://man.mtool.work/django/6.1/topics/email.html
PREV 1 2 3 4 5 6 7 8 9 10 NEXT