per page, with , order by , clip by
Results of 1 - 10 of about 100 for configuration (0.014 sec.)
Migrating email to mailers — Django 6.1 ドキュメント 14355
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 ... nd that Django substitutes during tests ), so can miss deprecation warnings that are only issued from the production email configuration. Consider running with deprecation warnings enabled in production to catch those deprecations. Or carefully review your co ... sword" : "password" , }, }, } The complete list of deprecated EMAIL_* settings and where they should be moved in a MAILERS configuration is: EMAIL_BACKEND becomes "BACKEND" . If your settings didn't define EMAIL_BACKEND , the default value was "django.core.ma ... il.backends.smtp.EmailBackend" (which is also the default if a MAILERS configuration doesn't specify the "BACKEND" ). EMAIL_FILE_PATH becomes "file_path" in "OPTIONS" (with "BACKEND" set to "django.core.mail ...
https://man.mtool.work/django/6.1/howto/mailers-migration.html
Migrating email to mailers — Django 6.1 ドキュメント 14264
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 ... nd that Django substitutes during tests ), so can miss deprecation warnings that are only issued from the production email configuration. Consider running with deprecation warnings enabled in production to catch those deprecations. Or carefully review your co ... sword" : "password" , }, }, } The complete list of deprecated EMAIL_* settings and where they should be moved in a MAILERS configuration is: EMAIL_BACKEND becomes "BACKEND" . If your settings didn't define EMAIL_BACKEND , the default value was "django.core.ma ... il.backends.smtp.EmailBackend" (which is also the default if a MAILERS configuration doesn't specify the "BACKEND" ). EMAIL_FILE_PATH becomes "file_path" in "OPTIONS" (with "BACKEND" set to "django.core.mail ...
https://man.mtool.work/django/6.1/howto/mailers-migration.html
メールを送信する — Django 6.1 ドキュメント 10129
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 ... ses Django's SMTP email backend , which sends using the standard SMTP protocol. This backend is useful for many production configurations, including SMTP servers in your own infrastructure and most commercial email service providers (ESPs). There are also thi ... development or testing you often don't want to send email at all. Django's test runner automatically overrides the MAILERS configuration to substitute Django's memory email backend . This prevents test cases from sending real email and gives them access to th ... erent services for transactional notifications and bulk marketing email, etc. The MAILERS setting can define multiple mail configurations. For example: import os MAILERS = { "default" : { "BACKEND" : "django.core.mail.backends.smtp.EmailBackend" , "OPTIONS" : ...
https://man.mtool.work/django/6.1/topics/email.html
メールを送信する — Django 6.1 ドキュメント 10129
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 ... ses Django's SMTP email backend , which sends using the standard SMTP protocol. This backend is useful for many production configurations, including SMTP servers in your own infrastructure and most commercial email service providers (ESPs). There are also thi ... development or testing you often don't want to send email at all. Django's test runner automatically overrides the MAILERS configuration to substitute Django's memory email backend . This prevents test cases from sending real email and gives them access to th ... erent services for transactional notifications and bulk marketing email, etc. The MAILERS setting can define multiple mail configurations. For example: import os MAILERS = { "default" : { "BACKEND" : "django.core.mail.backends.smtp.EmailBackend" , "OPTIONS" : ...
https://man.mtool.work/django/6.1/topics/email.html
Django 1.2.4 リリースノート — Django 6.1 ドキュメント 8517
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.2.4 リリースノート ¶ Django 1.2.4 へようこそ! This is the fourth "bugfix" release in the Django 1.2 series, improving the stability and per ... ne of the bugs fixed in Django 1.2.4 involves a set of circumstances whereby a running a test suite on a multiple database configuration could cause the original source database (i.e., the actual production database) to be dropped, causing catastrophic loss o ... introduce a new setting -- TEST_DEPENDENCIES -- that allows you to define any creation order dependencies in your database configuration. Most users -- even users with multiple-database configurations -- need not be concerned about the data loss bug, or the m ... anual configuration of TEST_DEPENDENCIES . See the original problem report documentation on controlling the creation order of test databases f ...
https://man.mtool.work/django/6.1/releases/1.2.4.html
Django 1.2.4 リリースノート — Django 6.1 ドキュメント 8439
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.2.4 リリースノート ¶ Django 1.2.4 へようこそ! This is the fourth "bugfix" release in the Django 1.2 series, improving the stability and per ... ne of the bugs fixed in Django 1.2.4 involves a set of circumstances whereby a running a test suite on a multiple database configuration could cause the original source database (i.e., the actual production database) to be dropped, causing catastrophic loss o ... introduce a new setting -- TEST_DEPENDENCIES -- that allows you to define any creation order dependencies in your database configuration. Most users -- even users with multiple-database configurations -- need not be concerned about the data loss bug, or the m ... anual configuration of TEST_DEPENDENCIES . See the original problem report documentation on controlling the creation order of test databases f ...
https://man.mtool.work/django/6.1/releases/1.2.4.html
LayerMapping データインポートユーティリティ — Django 6.1 ドキュメント 6579
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » LayerMapping データインポートユーティリティ ¶ LayerMapping クラスは、ベクトル空間データファイル (例: shapefile) の内容を GeoDjango モデルにマッピング ... an 'max_allowed_packet' bytes") Then the solution is to increase the value of the max_allowed_packet setting in your MySQL configuration. For example, the default value may be something low like one megabyte -- the setting may be modified in MySQL's configura ...
https://man.mtool.work/django/6.1/ref/contrib/gis/layermapping.html
Django 1.3.4 リリースノート — Django 6.1 ドキュメント 6579
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.3.4 リリースノート ¶ October 17, 2012 This is the fourth release in the Django 1.3 series. Host header poisoning ¶ Some parts of Django -- ... the web server to be properly configured; Django's documentation has for some time contained notes advising users on such configuration. Django's own built-in parsing of the Host header is, however, still vulnerable, as was reported to us recently. The Host ...
https://man.mtool.work/django/6.1/releases/1.3.4.html
Django 1.7 リリースノート — Django 6.1 ドキュメント 6579
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 以前からアップグ ... een refactored into an "app registry" where models modules no longer have a central role and where it's possible to attach configuration data to applications. Improvements thus far include: Applications can run code at startup, before Django does anything els ... e, with the ready() method of their configuration. Application labels are assigned correctly to models even when they're defined outside of models.py . You don't have to se ... entirely if an application doesn't have any models. Applications can be relabeled with the label attribute of application configurations, to work around label conflicts. The name of applications can be customized in the admin with the verbose_name of applica ...
https://man.mtool.work/django/6.1/releases/1.7.html
Django 1.9 リリースノート — Django 6.1 ドキュメント 6579
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.9 リリースノート ¶ December 1, 2015 Django 1.9 へようこそ! このリリースノートでは、 バージョン 1.9 の新機能 と、Django 1.8 以前からアップグ ... ようになりました。 The django.views.i18n.javascript_catalog() view now works correctly if used multiple times with different configurations on the same page. django.utils.timezone.make_aware() 関数が is_dst 引数を取って、DST 中の曖昧な時間を適切に処理できるよう ... ting migration from which migrations will be squashed. モデル ¶ QuerySet.bulk_create() now works on proxy models. Database configuration gained a TIME_ZONE option for interacting with databases that store datetimes in local time and don't support time zones w ... lity, the old class names will be kept as aliases to the new Origin class until Django 2.0. Changes to the default logging configuration ¶ To make it easier to write custom logging configurations, Django's default logging configuration no longer defines djang ...
https://man.mtool.work/django/6.1/releases/1.9.html
PREV 1 2 3 4 5 6 7 8 9 10 NEXT