per page, with , order by , clip by
Results of 1 - 10 of about 14 for covered (0.005 sec.)
Django 1.2.3 リリースノート — Django 6.1 ドキュメント 11658
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.2.3 リリースノート ¶ Django 1.2.3 fixed a couple of release problems in the 1.2.2 release and was released two days after 1.2.2. This relea ... se corrects the following problems: The patch applied for the security issue covered in Django 1.2.2 caused issues with non-ASCII responses using CSRF tokens. The patch also caused issues with some forms, mo ... oblems patch caused issues forms リリースノート fixed couple released days after corrects following applied security issue covered responses using tokens also most notably user クイック検索 Last update: 2026年10月09日 « previous | up | next » ...
https://man.mtool.work/django/6.1/releases/1.2.3.html
Unit tests — Django 6.1 ドキュメント 11483
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 ... ull requests and posts a comment with a diff coverage report. This helps reviewers see which lines in the changed code are covered by tests. What the coverage report shows: The coverage report posted on pull requests uses diff-cover to analyze only the ... lines that were changed or added in the PR. It shows: Lines that are covered by tests (✓) Lines that are not covered by tests (✗) Lines that cannot be covered (e.g., comments, blank lines) Important ... runs tests using PostgreSQL on Ubuntu. Code paths specific to other databases (SQLite, MySQL, Oracle) will appear as "not covered" even if database-specific tests exist. This is expected and acceptable. Platform-specific code: Similarly, code that only ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/unit-tests...
Unit tests — Django 6.1 ドキュメント 11483
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 ... ull requests and posts a comment with a diff coverage report. This helps reviewers see which lines in the changed code are covered by tests. What the coverage report shows: The coverage report posted on pull requests uses diff-cover to analyze only the ... lines that were changed or added in the PR. It shows: Lines that are covered by tests (✓) Lines that are not covered by tests (✗) Lines that cannot be covered (e.g., comments, blank lines) Important ... runs tests using PostgreSQL on Ubuntu. Code paths specific to other databases (SQLite, MySQL, Oracle) will appear as "not covered" even if database-specific tests exist. This is expected and acceptable. Platform-specific code: Similarly, code that only ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/unit-tests...
Django 1.2.3 リリースノート — Django 6.1 ドキュメント 11290
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.2.3 リリースノート ¶ Django 1.2.3 fixed a couple of release problems in the 1.2.2 release and was released two days after 1.2.2. This relea ... se corrects the following problems: The patch applied for the security issue covered in Django 1.2.2 caused issues with non-ASCII responses using CSRF tokens. The patch also caused issues with some forms, mo ... ms patch caused issues forms リリースノート fixed couple released two days after corrects following applied security issue covered 関連するページ Django 1.3.7 リリースノート Django 1.4.5 リリースノート Django 1.2.7 リリースノート Django 1.3.5 リリースノ ...
https://man.mtool.work/django/6.1/releases/1.2.3.html
Django におけるテスト — Django 6.1 ドキュメント 8262
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django におけるテスト ¶ 自動化テストは、モダンなウェブ開発者にとってバグを殺すために非常に役に立つツールです。テストのコレクション、 test suite を使 ... 。 The preferred way to write tests in Django is using the unittest module built-in to the Python standard library. This is covered in detail in the テストを書いて実行する document. You can also use any other Python test framework; Django provides an API ...
https://man.mtool.work/django/6.1/topics/testing/
Django におけるテスト — Django 6.1 ドキュメント 8262
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django におけるテスト ¶ 自動化テストは、モダンなウェブ開発者にとってバグを殺すために非常に役に立つツールです。テストのコレクション、 test suite を使 ... 。 The preferred way to write tests in Django is using the unittest module built-in to the Python standard library. This is covered in detail in the テストを書いて実行する document. You can also use any other Python test framework; Django provides an API ...
https://man.mtool.work/django/6.1/topics/testing/
Django 1.2 リリースノート — Django 6.1 ドキュメント 7684
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 ... ators. These are just the highlights; full details and a complete list of features may be found below . 参考 Django Advent covered the release of Django 1.2 with a series of articles and tutorials that cover some of the new features in depth. Wherever p ... n CSRF," where an attacking site tricks a user's browser into logging into a site with someone else's credentials, is also covered. Messages framework ¶ Django now includes a robust and configurable messages framework with built-in support for cookie- a ... ') and on methods (where the first argument is 'self', and the second argument is 'request'). Unfortunately, flaws were discovered in the code supporting this: it only works in limited circumstances, and produces errors that are very difficult to debug ...
https://man.mtool.work/django/6.1/releases/1.2.html
Django 1.2 リリースノート — Django 6.1 ドキュメント 7684
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 ... ators. These are just the highlights; full details and a complete list of features may be found below . 参考 Django Advent covered the release of Django 1.2 with a series of articles and tutorials that cover some of the new features in depth. Wherever p ... n CSRF," where an attacking site tricks a user's browser into logging into a site with someone else's credentials, is also covered. Messages framework ¶ Django now includes a robust and configurable messages framework with built-in support for cookie- a ... ') and on methods (where the first argument is 'self', and the second argument is 'request'). Unfortunately, flaws were discovered in the code supporting this: it only works in limited circumstances, and produces errors that are very difficult to debug ...
https://man.mtool.work/django/6.1/releases/1.2.html
Django 1.1 リリースノート — Django 6.1 ドキュメント 7492
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.1 リリースノート ¶ July 29, 2009 Django 1.1 へようこそ! Django 1.1 includes a number of nifty new features , lots of bug fixes, and an easy ... rySet with the results of the aggregate query. This feature is available as new aggregate() and annotate() methods, and is covered in detail in the ORM aggregation documentation . Query expressions ¶ Queries can now refer to another field on the query a ...
https://man.mtool.work/django/6.1/releases/1.1.html
Django 1.7 リリースノート — Django 6.1 ドキュメント 7492
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 以前からアップグ ... s that represent the model changes and which can be run on any development, staging or production database. Migrations are covered in their own documentation , but a few of the key features are: syncdb has been deprecated and replaced by migrate . Don't ... ble) creation of the default add, change, and delete permissions. Explicit OneToOneField for マルチテーブル継承 are now discovered in abstract classes. It is now possible to avoid creating a backward relation for OneToOneField by setting its related_nam ... rrorList knows how to handle instances of ValidationError . Most use-cases that warranted using these private APIs are now covered by the newly introduced Form.add_error() method: # Old pattern: try : ... except ValidationError as e : self . _errors = e ...
https://man.mtool.work/django/6.1/releases/1.7.html
PREV 1 2 NEXT