per page, with , order by , clip by
Results of 1 - 10 of about 238 for Settings (0.003 sec.)
Djangoの設定 — Django 6.1 ドキュメント 10634
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Djangoの設定 ¶ Djangoの設定ファイルには、インストールしたDjangoの全ての設定が含まれています。このドキュメントでは、各設定の役割と、どのような設定を利 ... えば: MY_SETTING = [ str ( i ) for i in range ( 30 )] 他の設定ファイルから値を import できます。 設定ファイルの指定 ¶ DJANGO_SETTINGS_MODULE ¶ Django を使うとき、どの設定を使うかを Django に伝える必要があります。そのためには環境変数 DJANGO_SETTINGS_MODULE ... を使います。 The value of DJANGO_SETTINGS_MODULE should be in Python path syntax, e.g. mysite.settings . Note that the settings module should be on the Python sys.p ... 数を予め指定しておくか、ユーティリティを起動する度に設定モジュールを明示的に渡します。 例 (Unix Bash シェル): export DJANGO_SETTINGS_MODULE = mysite.settings django-admin runserver 例 (Windows シェル): set DJANGO_SETTINGS_MODULE=mysite.settings django-adm ...
https://man.mtool.work/django/6.1/topics/settings.html
Djangoの設定 — Django 6.1 ドキュメント 10634
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Djangoの設定 ¶ Djangoの設定ファイルには、インストールしたDjangoの全ての設定が含まれています。このドキュメントでは、各設定の役割と、どのような設定を利 ... えば: MY_SETTING = [ str ( i ) for i in range ( 30 )] 他の設定ファイルから値を import できます。 設定ファイルの指定 ¶ DJANGO_SETTINGS_MODULE ¶ Django を使うとき、どの設定を使うかを Django に伝える必要があります。そのためには環境変数 DJANGO_SETTINGS_MODULE ... を使います。 The value of DJANGO_SETTINGS_MODULE should be in Python path syntax, e.g. mysite.settings . Note that the settings module should be on the Python sys.p ... 数を予め指定しておくか、ユーティリティを起動する度に設定モジュールを明示的に渡します。 例 (Unix Bash シェル): export DJANGO_SETTINGS_MODULE = mysite.settings django-admin runserver 例 (Windows シェル): set DJANGO_SETTINGS_MODULE=mysite.settings django-adm ...
https://man.mtool.work/django/6.1/topics/settings.html
Unit tests — Django 6.1 ドキュメント 9788
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Unit tests ¶ Django comes with a test suite of its own, in the tests directory of the code base. It's our policy to make sure all tests pass at all ... y. See Running all the tests for details on installing the optional test dependencies. Running the tests requires a Django settings module that defines the databases to use. To help you get started, Django provides and uses a sample settings module that ... uses the SQLite database. See Using another settings module to learn how to use a different settings module to run the tests with a different database. Having problems? See ト ... n -m pip install tox $ tox ...\> py -m pip install tox ...\> tox By default, tox runs the test suite with the bundled test settings file for SQLite, black , blacken-docs , flake8 , isort , lint-docs , zizmor , and the documentation spelling checker. In a ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/unit-tests...
Unit tests — Django 6.1 ドキュメント 9788
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Unit tests ¶ Django comes with a test suite of its own, in the tests directory of the code base. It's our policy to make sure all tests pass at all ... y. See Running all the tests for details on installing the optional test dependencies. Running the tests requires a Django settings module that defines the databases to use. To help you get started, Django provides and uses a sample settings module that ... uses the SQLite database. See Using another settings module to learn how to use a different settings module to run the tests with a different database. Having problems? See ト ... n -m pip install tox $ tox ...\> py -m pip install tox ...\> tox By default, tox runs the test suite with the bundled test settings file for SQLite, black , blacken-docs , flake8 , isort , lint-docs , zizmor , and the documentation spelling checker. In a ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/unit-tests...
Migrating email to mailers — Django 6.1 ドキュメント 9584
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 ... -party packages that send email, verify their compatibility with MAILERS before making other changes. Update email-related settings . Run with deprecation warnings enabled (see 廃止予定警告を解決する ) to identify other code needing updates. 注釈 Running ... ting AdminEmailHandler email_backend Ignoring transient failures in error reporting バージョン 6.1 で非推奨: The following settings and functions will be removed in Django 2028: EMAIL_BACKEND , EMAIL_FILE_PATH , EMAIL_HOST , EMAIL_HOST_PASSWORD , EMAIL_H ... and auth_password arguments to send_mail() and send_mass_mail() The email_backend argument to AdminEmailHandler Migrating settings ¶ Often, the only change needed to migrate to mailers is updating email-related settings. In your project's settings, defi ...
https://man.mtool.work/django/6.1/howto/mailers-migration.html
Migrating email to mailers — Django 6.1 ドキュメント 9584
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 ... -party packages that send email, verify their compatibility with MAILERS before making other changes. Update email-related settings . Run with deprecation warnings enabled (see 廃止予定警告を解決する ) to identify other code needing updates. 注釈 Running ... ting AdminEmailHandler email_backend Ignoring transient failures in error reporting バージョン 6.1 で非推奨: The following settings and functions will be removed in Django 2028: EMAIL_BACKEND , EMAIL_FILE_PATH , EMAIL_HOST , EMAIL_HOST_PASSWORD , EMAIL_H ... and auth_password arguments to send_mail() and send_mass_mail() The email_backend argument to AdminEmailHandler Migrating settings ¶ Often, the only change needed to migrate to mailers is updating email-related settings. In your project's settings, defi ...
https://man.mtool.work/django/6.1/howto/mailers-migration.html
Coding style — Django 6.1 ドキュメント 7140
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Coding style ¶ Please follow these coding standards when writing code for inclusion in Django. Pre-commit checks ¶ pre-commit is a framework for man ... Model ( models . Model ): class Direction ( models . TextChoices ): UP = "U" , "Up" DOWN = "D" , "Down" Use of django.conf.settings ¶ Modules should not in general use settings stored in django.conf.settings at the top level (i.e. evaluated when the modu ... le is imported). The explanation for this is as follows: Manual configuration of settings (i.e. not relying on the DJANGO_SETTINGS_MODULE environment variable) is allowed and possible as follows: from django.conf ... import settings settings . configure ({}, SOME_SETTING = "foo" ) However, if any setting is accessed before the settings.configure line, t ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/coding-sty...
Coding style — Django 6.1 ドキュメント 7099
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Coding style ¶ Please follow these coding standards when writing code for inclusion in Django. Pre-commit checks ¶ pre-commit is a framework for man ... Model ( models . Model ): class Direction ( models . TextChoices ): UP = "U" , "Up" DOWN = "D" , "Down" Use of django.conf.settings ¶ Modules should not in general use settings stored in django.conf.settings at the top level (i.e. evaluated when the modu ... le is imported). The explanation for this is as follows: Manual configuration of settings (i.e. not relying on the DJANGO_SETTINGS_MODULE environment variable) is allowed and possible as follows: from django.conf ... import settings settings . configure ({}, SOME_SETTING = "foo" ) However, if any setting is accessed before the settings.configure line, t ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/coding-sty...
Django 1.7.11 リリースノート — Django 6.1 ドキュメント 7099
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.7.11 リリースノート ¶ November 24, 2015 Django 1.7.11 fixes a security issue and a data loss bug in 1.7.10. Fixed settings leak possibility ... filter, e.g. {{ last_updated|date:user_date_format }} , then a malicious user could obtain any secret in the application's settings by specifying a settings key instead of a date format. e.g. "SECRET_KEY" instead of "j/m/Y" . To remedy this, the underlyi ... n used by the date template filter, django.utils.formats.get_format() , now only allows accessing the date/time formatting settings. バグ修正 ¶ Fixed a data loss possibility with Prefetch if to_attr is set to a ManyToManyField ( #25693 ). 目次 Django 1.7 ... .11 リリースノート Fixed settings leak possibility in date template filter バグ修正 前のトピックへ Django 1.8 リリースノート 次のトピックへ Django 1.7.10 リ ...
https://man.mtool.work/django/6.1/releases/1.7.11.html
Django 1.7.11 リリースノート — Django 6.1 ドキュメント 6895
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.7.11 リリースノート ¶ November 24, 2015 Django 1.7.11 fixes a security issue and a data loss bug in 1.7.10. Fixed settings leak possibility ... filter, e.g. {{ last_updated|date:user_date_format }} , then a malicious user could obtain any secret in the application's settings by specifying a settings key instead of a date format. e.g. "SECRET_KEY" instead of "j/m/Y" . To remedy this, the underlyi ... n used by the date template filter, django.utils.formats.get_format() , now only allows accessing the date/time formatting settings. バグ修正 ¶ Fixed a data loss possibility with Prefetch if to_attr is set to a ManyToManyField ( #25693 ). 目次 Django 1.7 ... .11 リリースノート Fixed settings leak possibility in date template filter バグ修正 前のトピックへ Django 1.8 リリースノート 次のトピックへ Django 1.7.10 リ ...
https://man.mtool.work/django/6.1/releases/1.7.11.html
PREV 1 2 3 4 5 6 7 8 9 10 NEXT