... d far more quickly than those without a solution. Typo fixes and trivial documentation changes ¶ If you are fixing a really trivial issue, for example changing a word in the documentation, the preferred way to ... Going through the steps of claiming tickets is overkill in some cases. In the case of small changes, such as typos in the documentation or small bugs that will only take a few minutes to fix, you don't need to jump through the hoops of claiming tickets. Subm ... ing again. If the code adds a new feature, or modifies the behavior of an existing feature, the change should also contain documentation. When you think your work is ready to be reviewed, send a GitHub pull request . If you can't send a pull request for some ... ... d far more quickly than those without a solution. Typo fixes and trivial documentation changes ¶ If you are fixing a really trivial issue, for example changing a word in the documentation, the preferred way to ... Going through the steps of claiming tickets is overkill in some cases. In the case of small changes, such as typos in the documentation or small bugs that will only take a few minutes to fix, you don't need to jump through the hoops of claiming tickets. Subm ... ing again. If the code adds a new feature, or modifies the behavior of an existing feature, the change should also contain documentation. When you think your work is ready to be reviewed, send a GitHub pull request . If you can't send a pull request for some ... ... xed more than 2,000 bugs, and edited, added, or removed around 350,000 lines of code. We've also added 40,000 lines of new documentation, and greatly improved what was already there. In fact, new documentation is one of our favorite features of Django 1.0, so ... we might as well start there. First, there's a new documentation site: https://docs.djangoproject.com/ The documentation has been greatly improved, cleaned up, and generally made awesome. ... There's now dedicated search, indexes, and more. We can't possibly document everything that's new in 1.0, but the documentation will be your definitive guide. Anywhere you see something like: New in Django 1.0: This feature is new in Django 1.0 You'l ... ... xed more than 2,000 bugs, and edited, added, or removed around 350,000 lines of code. We've also added 40,000 lines of new documentation, and greatly improved what was already there. In fact, new documentation is one of our favorite features of Django 1.0, so ... we might as well start there. First, there's a new documentation site: https://docs.djangoproject.com/ The documentation has been greatly improved, cleaned up, and generally made awesome. ... There's now dedicated search, indexes, and more. We can't possibly document everything that's new in 1.0, but the documentation will be your definitive guide. Anywhere you see something like: New in Django 1.0: This feature is new in Django 1.0 You'l ... ... ns. It has been demonstrated that this mechanism cannot be made reliable enough for general-purpose use, and that (despite documentation to the contrary) its inclusion in Django may lead application developers to assume that the value of REMOTE_ADDR is "safe" ... の新機能 ¶ Quite a bit: since Django 1.0, we've made 1,290 code commits, fixed 1,206 bugs, and added roughly 10,000 lines of documentation. The major new features in Django 1.1 are: ORM improvements ¶ Two major enhancements have been added to Django's object-re ... uery. 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 and can traverse relationships to refer to field ... ... ns. It has been demonstrated that this mechanism cannot be made reliable enough for general-purpose use, and that (despite documentation to the contrary) its inclusion in Django may lead application developers to assume that the value of REMOTE_ADDR is "safe" ... の新機能 ¶ Quite a bit: since Django 1.0, we've made 1,290 code commits, fixed 1,206 bugs, and added roughly 10,000 lines of documentation. The major new features in Django 1.1 are: ORM improvements ¶ Two major enhancements have been added to Django's object-re ... uery. 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 and can traverse relationships to refer to field ... ... マで表示されます。これはOKです!あなたのローカルマシンで変更がうまくいけば、 ウェブサイトでもうまくいくでしょう。 Automating documentation rebuilds ¶ sphinx-autobuild can be used to automatically rebuild the documentation and reload the documentation page in th ... ぶには reStructuredText reference を参照してください。 このページを編集するには、例えば docs/internals/contributing/writing-documentation.txt というファイルを編集し、 make html でHTMLを再構築します。 Documentation quality checks ¶ Several checks help maintain ... Django's documentation quality, including spelling , code block formatting , and documentation style . These checks are run automatically in CI a ... ... マで表示されます。これはOKです!あなたのローカルマシンで変更がうまくいけば、 ウェブサイトでもうまくいくでしょう。 Automating documentation rebuilds ¶ sphinx-autobuild can be used to automatically rebuild the documentation and reload the documentation page in th ... ぶには reStructuredText reference を参照してください。 このページを編集するには、例えば docs/internals/contributing/writing-documentation.txt というファイルを編集し、 make html でHTMLを再構築します。 Documentation quality checks ¶ Several checks help maintain ... Django's documentation quality, including spelling , code block formatting , and documentation style . These checks are run automatically in CI a ... ... + Needs fixes) This means the ticket has been reviewed, and has been found to need further work. "Needs tests" and "Needs documentation" are self-explanatory. "Patch needs improvement" will generally be accompanied by a comment on the ticket explaining what ... ed solution. These will be reviewed to ensure they adhere to the documented guidelines . The following three fields (Needs documentation, Needs tests, Patch needs improvement) apply only if a patch has been supplied. Needs documentation (ドキュメンテーションが ... 必要) ¶ This flag is used for tickets with patches that need associated documentation. Complete documentation of features is a prerequisite before we can check them into the codebase. Needs tests (テストが必要 ... ... + Needs fixes) This means the ticket has been reviewed, and has been found to need further work. "Needs tests" and "Needs documentation" are self-explanatory. "Patch needs improvement" will generally be accompanied by a comment on the ticket explaining what ... ed solution. These will be reviewed to ensure they adhere to the documented guidelines . The following three fields (Needs documentation, Needs tests, Patch needs improvement) apply only if a patch has been supplied. Needs documentation (ドキュメンテーションが ... 必要) ¶ This flag is used for tickets with patches that need associated documentation. Complete documentation of features is a prerequisite before we can check them into the codebase. Needs tests (テストが必要 ... 2026年10月08日