per page, with , order by , clip by
Results of 1 - 10 of about 122 for automatically (0.006 sec.)
Django 1.0.1 リリースノート — Django 6.1 ドキュメント 14318
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.0.1 リリースノート ¶ Django 1.0.1 へようこそ! This is the first "bugfix" release in the Django 1.0 series, improving the stability and perf ... y queries. Multiple fixes for inline forms in formsets. Multiple fixes for unique and unique_together model constraints in automatically-generated forms. Fixed support for custom callable upload_to declarations when handling file uploads through automatically ... on of autoescaping for literal strings passed to the join template filter. Previously, literal strings passed to join were automatically escaped, contrary to the documented behavior for autoescaping and literal strings . Literal strings passed to join are no ... longer automatically escaped, meaning you must now manually escape them; this is an incompatibility if you were relying on this bug, but not if ...
https://man.mtool.work/django/6.1/releases/1.0.1.html
Django 1.0.1 リリースノート — Django 6.1 ドキュメント 13923
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.0.1 リリースノート ¶ Django 1.0.1 へようこそ! This is the first "bugfix" release in the Django 1.0 series, improving the stability and perf ... y queries. Multiple fixes for inline forms in formsets. Multiple fixes for unique and unique_together model constraints in automatically-generated forms. Fixed support for custom callable upload_to declarations when handling file uploads through automatically ... on of autoescaping for literal strings passed to the join template filter. Previously, literal strings passed to join were automatically escaped, contrary to the documented behavior for autoescaping and literal strings . Literal strings passed to join are no ... longer automatically escaped, meaning you must now manually escape them; this is an incompatibility if you were relying on this bug, but not if ...
https://man.mtool.work/django/6.1/releases/1.0.1.html
Unit tests — Django 6.1 ドキュメント 8544
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 ... comment out its line in requirements/py3.txt and continue with ./runtests.py . Tests that require pylibmc will be skipped automatically. See Running all the tests for details on installing the optional test dependencies. Running the tests requires a Django s ... .py --selenium=firefox,chrome See the selenium.webdriver package for the list of available browsers. Specifying --selenium automatically sets --tags=selenium to run only the tests that require selenium. Some browsers (e.g. Chrome or Firefox) support headless ... st code or external code included in Django). Code coverage on pull requests ¶ Django's continuous integration (CI) system automatically runs code coverage analysis on pull requests and posts a comment with a diff coverage report. This helps reviewers see whi ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/unit-tests...
Unit tests — Django 6.1 ドキュメント 8544
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 ... comment out its line in requirements/py3.txt and continue with ./runtests.py . Tests that require pylibmc will be skipped automatically. See Running all the tests for details on installing the optional test dependencies. Running the tests requires a Django s ... .py --selenium=firefox,chrome See the selenium.webdriver package for the list of available browsers. Specifying --selenium automatically sets --tags=selenium to run only the tests that require selenium. Some browsers (e.g. Chrome or Firefox) support headless ... st code or external code included in Django). Code coverage on pull requests ¶ Django's continuous integration (CI) system automatically runs code coverage analysis on pull requests and posts a comment with a diff coverage report. This helps reviewers see whi ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/unit-tests...
Django 3.2 リリースノート — Django 6.1 ドキュメント 8136
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 3.2 リリースノート ¶ April 6, 2021 Django 3.2 へようこそ! このリリースノートでは、 バージョン 3.2 の新機能 と、Django 3.1 以前からアップグレー ... _init__.py . When the apps.py submodule exists and defines a single AppConfig subclass, Django now uses that configuration automatically, so you can remove default_app_config . default_app_config made it possible to declare only the application's path in INST ... checks were performed. Support for colored terminal output on Windows is updated. Various modern terminal environments are automatically detected, and the options for enabling support in other cases are improved. See シンタックスカラーリング for more details. ... s nested relations. The of argument of QuerySet.select_for_update() is now allowed on MySQL 8.0.1+. Value() expression now automatically resolves its output_field to the appropriate Field subclass based on the type of its provided value for bool , bytes , flo ...
https://man.mtool.work/django/6.1/releases/3.2.html
Django 3.2 リリースノート — Django 6.1 ドキュメント 8136
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 3.2 リリースノート ¶ April 6, 2021 Django 3.2 へようこそ! このリリースノートでは、 バージョン 3.2 の新機能 と、Django 3.1 以前からアップグレー ... _init__.py . When the apps.py submodule exists and defines a single AppConfig subclass, Django now uses that configuration automatically, so you can remove default_app_config . default_app_config made it possible to declare only the application's path in INST ... checks were performed. Support for colored terminal output on Windows is updated. Various modern terminal environments are automatically detected, and the options for enabling support in other cases are improved. See シンタックスカラーリング for more details. ... s nested relations. The of argument of QuerySet.select_for_update() is now allowed on MySQL 8.0.1+. Value() expression now automatically resolves its output_field to the appropriate Field subclass based on the type of its provided value for bool , bytes , flo ...
https://man.mtool.work/django/6.1/releases/3.2.html
メールを送信する — Django 6.1 ドキュメント 7542
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 ... add other sending features. During 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 re ... This can be fixed with a try - finally statement, but using the backend instance as a context manager is preferable, as it automatically calls open() and close() as needed. This is equivalent to the previous example, but uses the backend as a context manager ... e mail.mailers[...] as a context manager. with mail . mailers [ "notifications" ] as backend : # The backend connection is automatically opened inside the context. email1 = mail . EmailMessage ( "Hi" , "Message" , None , [ "to1@example.com" ]) backend . send_ ...
https://man.mtool.work/django/6.1/topics/email.html
メールを送信する — Django 6.1 ドキュメント 7542
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 ... add other sending features. During 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 re ... This can be fixed with a try - finally statement, but using the backend instance as a context manager is preferable, as it automatically calls open() and close() as needed. This is equivalent to the previous example, but uses the backend as a context manager ... e mail.mailers[...] as a context manager. with mail . mailers [ "notifications" ] as backend : # The backend connection is automatically opened inside the context. email1 = mail . EmailMessage ( "Hi" , "Message" , None , [ "to1@example.com" ]) backend . send_ ...
https://man.mtool.work/django/6.1/topics/email.html
Django 1.0 リリースノート — Django 6.1 ドキュメント 6949
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.0 リリースノート ¶ Django 1.0 へようこそ! We've been looking forward to this moment for over three years, and it's finally here. Django 1.0 ... なエスケープ ¶ To provide improved security against cross-site scripting (XSS) vulnerabilities, Django's template system now automatically escapes the output of variables. This behavior is configurable, and allows both variables and larger template constructs t ... relations for details. INSERT / UPDATE distinction ¶ Although Django's default behavior of having a model's save() method automatically determine whether to perform an INSERT or an UPDATE at the SQL level is suitable for the majority of cases, there are occa ...
https://man.mtool.work/django/6.1/releases/1.0.html
Django 1.6 リリースノート — Django 6.1 ドキュメント 6949
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.6 リリースノート ¶ 注釈 Dedicated to Malcolm Tredinnick On March 17, 2013, the Django project and the free software community lost a very d ... tain greater consistency with Python's unittest module, the new test runner ( django.test.runner.DiscoverRunner ) does not automatically support some types of tests that were supported by the previous runner: Tests in models.py and tests/__init__.py files wil ... l no longer be found and run. Move them to a file whose name begins with test . Doctests will no longer be automatically discovered. To integrate doctests in your test suite, follow the recommendations in the Python documentation . Django bund ... and all fields would be used. This can lead to security problems where fields are added to the model and, unintentionally, automatically become editable by end users. In some cases, particular with boolean fields, it is possible for this problem to be complet ...
https://man.mtool.work/django/6.1/releases/1.6.html
PREV 1 2 3 4 5 6 7 8 9 10 NEXT