per page, with , order by , clip by
Results of 1 - 10 of about 62 for implementation (0.018 sec.)
チケットをトリアージする — Django 6.1 ドキュメント 12715
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » チケットをトリアージする ¶ Django uses Trac for managing the work on the code base. Trac is a community-tended garden of the bugs people have found ... s the typical lifecycle of a ticket: Alice creates a ticket and opens an incomplete pull request (missing tests, incorrect implementation). Bob reviews the pull request, marks the ticket as "Accepted", sets the flags "needs tests" and "patch needs improvement" ... waiting on author" queue within the "accepted" stage. Alice updates the pull request, adding tests (but not yet fixing the implementation), and removes the two flags. The ticket moves into the "needs PR review" queue. Charlie reviews the pull request, sets the ... "patch needs improvement" flag again, and leaves another comment suggesting changes to the implementation. The ticket moves back to the "waiting on author" queue. Alice updates the pull request again, this time fixing the implem ...
https://man.mtool.work/django/6.1/internals/contributing/triaging-tickets.html
チケットをトリアージする — Django 6.1 ドキュメント 11227
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » チケットをトリアージする ¶ Django uses Trac for managing the work on the code base. Trac is a community-tended garden of the bugs people have found ... s the typical lifecycle of a ticket: Alice creates a ticket and opens an incomplete pull request (missing tests, incorrect implementation). Bob reviews the pull request, marks the ticket as "Accepted", sets the flags "needs tests" and "patch needs improvement" ... waiting on author" queue within the "accepted" stage. Alice updates the pull request, adding tests (but not yet fixing the implementation), and removes the two flags. The ticket moves into the "needs PR review" queue. Charlie reviews the pull request, sets the ... "patch needs improvement" flag again, and leaves another comment suggesting changes to the implementation. The ticket moves back to the "waiting on author" queue. Alice updates the pull request again, this time fixing the implem ...
https://man.mtool.work/django/6.1/internals/contributing/triaging-tickets.html
Django 1.2 リリースノート — Django 6.1 ドキュメント 11227
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.2 リリースノート ¶ 2010 年 5 月 17 日 Django 1.2 へようこそ! Nearly a year in the making, Django 1.2 packs an impressive list of new featur ... ベルのパーミッション ¶ A foundation for specifying permissions at the per-object level has been added. Although there is no implementation of this in core, a custom authentication backend can provide this implementation and it will be used by django.contrib.aut ... d mail sending methods to use those facilities. This also makes it easier to debug mail sending. Django ships with backend implementations that allow you to send email to a file , to the console , or to memory . You can even configure all email to be thrown aw ... o 1.3 release. If you have developed your own custom template loaders we suggest to consider porting them to a class-based implementation because the code for backwards compatibility with function-based loaders starts its deprecation process in Django 1.2 and ...
https://man.mtool.work/django/6.1/releases/1.2.html
Django 1.2 リリースノート — Django 6.1 ドキュメント 11227
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.2 リリースノート ¶ 2010 年 5 月 17 日 Django 1.2 へようこそ! Nearly a year in the making, Django 1.2 packs an impressive list of new featur ... ベルのパーミッション ¶ A foundation for specifying permissions at the per-object level has been added. Although there is no implementation of this in core, a custom authentication backend can provide this implementation and it will be used by django.contrib.aut ... d mail sending methods to use those facilities. This also makes it easier to debug mail sending. Django ships with backend implementations that allow you to send email to a file , to the console , or to memory . You can even configure all email to be thrown aw ... o 1.3 release. If you have developed your own custom template loaders we suggest to consider porting them to a class-based implementation because the code for backwards compatibility with function-based loaders starts its deprecation process in Django 1.2 and ...
https://man.mtool.work/django/6.1/releases/1.2.html
Django 4.0 リリースノート — Django 6.1 ドキュメント 10114
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 4.0 リリースノート ¶ 2021年12月7日 Django 4.0 へようこそ! このリリースノートでは、 バージョン 4.0 の新機能 と、Django 3.2 以前からアップグレー ... します。 The Django 3.2.x series is the last to support Python 3.6 and 3.7. Django 4.0 の新機能 ¶ zoneinfo default timezone implementation ¶ The Python standard library's zoneinfo is now the default timezone implementation in Django. This is the next step in th ... m using pytz to using zoneinfo . Django 3.2 allowed the use of non- pytz time zones. Django 4.0 makes zoneinfo the default implementation. Support for pytz is now deprecated and will be removed in Django 5.0. zoneinfo is part of the Python standard library fro ... tting is removed. 目次 Django 4.0 リリースノート Python バージョン間の互換性 Django 4.0 の新機能 zoneinfo default timezone implementation Functional unique constraints scrypt password hasher Redis cache backend Template based form rendering マイナーな機能 djan ...
https://man.mtool.work/django/6.1/releases/4.0.html
Django 4.0 リリースノート — Django 6.1 ドキュメント 10114
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 4.0 リリースノート ¶ 2021年12月7日 Django 4.0 へようこそ! このリリースノートでは、 バージョン 4.0 の新機能 と、Django 3.2 以前からアップグレー ... します。 The Django 3.2.x series is the last to support Python 3.6 and 3.7. Django 4.0 の新機能 ¶ zoneinfo default timezone implementation ¶ The Python standard library's zoneinfo is now the default timezone implementation in Django. This is the next step in th ... m using pytz to using zoneinfo . Django 3.2 allowed the use of non- pytz time zones. Django 4.0 makes zoneinfo the default implementation. Support for pytz is now deprecated and will be removed in Django 5.0. zoneinfo is part of the Python standard library fro ... tting is removed. 目次 Django 4.0 リリースノート Python バージョン間の互換性 Django 4.0 の新機能 zoneinfo default timezone implementation Functional unique constraints scrypt password hasher Redis cache backend Template based form rendering マイナーな機能 djan ...
https://man.mtool.work/django/6.1/releases/4.0.html
Migrating email to mailers — Django 6.1 ドキュメント 8250
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 ... o have several different expectations for the behavior, many of which don't match the actual (and email backend-dependent) implementation. Consider removing fail_silently entirely if there is not a specific need for it. Calls with fail_silently=True should be ... s both transient network glitches and SMTP configuration problems (just like the existing SMTP email backend fail_silently implementation). To ignore end user typos in to addresses and other delivery problems, remove the fail_silently argument. Recipient error ... ilent behavior, see Ignoring transient failures in error reporting . Migrating custom email backends ¶ Custom EmailBackend implementations may need to be updated for compatibility with mailers. In the backend's __init__() method, accept explicit keyword argume ...
https://man.mtool.work/django/6.1/howto/mailers-migration.html
How to use Django's Content Security Policy — Django 6.1 ドキュメント 8250
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » How to use Django's Content Security Policy ¶ Basic config ¶ Content Security Policy (CSP) を有効にするには、Django プロジェクトで次のように設定しま ... header are generated within the same request and not served from cache. See the reference documentation on Nonce usage for implementation details and important caching considerations. 目次 How to use Django's Content Security Policy Basic config Nonce config 前 ...
https://man.mtool.work/django/6.1/howto/csp.html
Migrating email to mailers — Django 6.1 ドキュメント 8250
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 ... o have several different expectations for the behavior, many of which don't match the actual (and email backend-dependent) implementation. Consider removing fail_silently entirely if there is not a specific need for it. Calls with fail_silently=True should be ... s both transient network glitches and SMTP configuration problems (just like the existing SMTP email backend fail_silently implementation). To ignore end user typos in to addresses and other delivery problems, remove the fail_silently argument. Recipient error ... ilent behavior, see Ignoring transient failures in error reporting . Migrating custom email backends ¶ Custom EmailBackend implementations may need to be updated for compatibility with mailers. In the backend's __init__() method, accept explicit keyword argume ...
https://man.mtool.work/django/6.1/howto/mailers-migration.html
How to use Django's Content Security Policy — Django 6.1 ドキュメント 7874
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » How to use Django's Content Security Policy ¶ Basic config ¶ Content Security Policy (CSP) を有効にするには、Django プロジェクトで次のように設定しま ... header are generated within the same request and not served from cache. See the reference documentation on Nonce usage for implementation details and important caching considerations. 目次 How to use Django's Content Security Policy Basic config Nonce config 前 ...
https://man.mtool.work/django/6.1/howto/csp.html
PREV 1 2 3 4 5 6 7 NEXT