... handle them, see プルリクエストの取り扱い . Below, we are going to show how to create a GitHub pull request containing the changes for Trac ticket #xxxxx. By creating a fully-ready pull request, you will make the reviewer's job easier, meaning that your ... o: git checkout -b ticket_xxxxx_1_4 upstream/stable/1.4.x Assume the work is carried on the ticket_xxxxx branch. Make some changes and commit them: git commit When writing the commit message, follow the commit message guidelines to ease the work of the ... delines for more details, documentation and tests, if needed -- actually tests are always needed, except for documentation changes. The test suite must pass and the documentation must build without warnings. Once you have created your pull request, you ... ... apps to 1.0. The first part of this document includes the common changes needed to run with 1.0. If after going through the first part your code still breaks, check the section Less-common Change ... いてより深く説明しています。移植ガイドは、あなたのコードを素早く更新するための手助けをすることに重点を置いています。 Common changes ¶ This section describes the changes between 0.96 and 1.0 that most users will need to make. Use Unicode ¶ Change string l ... updating to use Unicode literals will prevent some obscure problems. See Unicode データ for full details. モデル ¶ Common changes to your models file: Rename maxlength to max_length ¶ Rename your maxlength argument to max_length (this was changed to be ... ... apps to 1.0. The first part of this document includes the common changes needed to run with 1.0. If after going through the first part your code still breaks, check the section Less-common Change ... いてより深く説明しています。移植ガイドは、あなたのコードを素早く更新するための手助けをすることに重点を置いています。 Common changes ¶ This section describes the changes between 0.96 and 1.0 that most users will need to make. Use Unicode ¶ Change string l ... updating to use Unicode literals will prevent some obscure problems. See Unicode データ for full details. モデル ¶ Common changes to your models file: Rename maxlength to max_length ¶ Rename your maxlength argument to max_length (this was changed to be ... ... handle them, see プルリクエストの取り扱い . Below, we are going to show how to create a GitHub pull request containing the changes for Trac ticket #xxxxx. By creating a fully-ready pull request, you will make the reviewer's job easier, meaning that your ... o: git checkout -b ticket_xxxxx_1_4 upstream/stable/1.4.x Assume the work is carried on the ticket_xxxxx branch. Make some changes and commit them: git commit When writing the commit message, follow the commit message guidelines to ease the work of the ... delines for more details, documentation and tests, if needed -- actually tests are always needed, except for documentation changes. The test suite must pass and the documentation must build without warnings. Once you have created your pull request, you ... ... ere have been a few small backwards-incompatible changes since 0.95, but the upgrade process should be fairly simple and should not require major changes to existing applications. ... However, we're also releasing 0.96 now because we have a set of backwards-incompatible changes scheduled for the near future. Once completed, they will involve some code changes for application developers, so we recom ... go 0.96 until the next official release; then you'll be able to upgrade in one step instead of needing to make incremental changes to keep up with the development version of Django. 後方互換性のない変更 ¶ The following changes may require you to update ... ... ere have been a few small backwards-incompatible changes since 0.95, but the upgrade process should be fairly simple and should not require major changes to existing applications. ... However, we're also releasing 0.96 now because we have a set of backwards-incompatible changes scheduled for the near future. Once completed, they will involve some code changes for application developers, so we recom ... go 0.96 until the next official release; then you'll be able to upgrade in one step instead of needing to make incremental changes to keep up with the development version of Django. 後方互換性のない変更 ¶ The following changes may require you to update ... ... 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 provide ... radio button in the "Action" section. Your username will be filled in the text box by default. Finally, click the "Submit changes" button at the bottom to save. 注釈 If your change is not trivial , you have the option to sign and submit a Contributor L ... h tickets should be claimed? ¶ 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 ... ... es and lots of bug fixes. These release notes cover the new features, as well as important changes you'll want to be aware of when upgrading from Django 1.1 or older versions. オーバービュー ¶ Django 1.2 introduces severa ... policy. However, a handful of features have changed in ways that, for some users, will be backwards-incompatible. The big changes are: Support for Python 2.3 has been dropped. See the full notes below. The new CSRF protection framework is not backwards ... ved in Django 1.4. However, upgrading to the new CSRF protection framework requires a few important backwards-incompatible changes, detailed in CSRF Protection , below. Authors of custom Field subclasses should be aware that a number of methods have had ... ... 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 provide ... radio button in the "Action" section. Your username will be filled in the text box by default. Finally, click the "Submit changes" button at the bottom to save. 注釈 If your change is not trivial , you have the option to sign and submit a Contributor L ... h tickets should be claimed? ¶ 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 ... ... es and lots of bug fixes. These release notes cover the new features, as well as important changes you'll want to be aware of when upgrading from Django 1.1 or older versions. オーバービュー ¶ Django 1.2 introduces severa ... policy. However, a handful of features have changed in ways that, for some users, will be backwards-incompatible. The big changes are: Support for Python 2.3 has been dropped. See the full notes below. The new CSRF protection framework is not backwards ... ved in Django 1.4. However, upgrading to the new CSRF protection framework requires a few important backwards-incompatible changes, detailed in CSRF Protection , below. Authors of custom Field subclasses should be aware that a number of methods have had ... 2026年10月08日