... 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 Changes for ... することに重点を置いています。 Common changes ¶ This section describes the changes between 0.96 and 1.0 that most users will need to make. Use Unicode ¶ Change string literals ( 'foo' ) into Unicode literals ( u'foo' ). Django now uses Unicode strings ... emove the core argument from your model fields. It is no longer necessary, since the equivalent functionality (part of inline editing ) is handled differently by the admin interface now. You don't have to worry about inline editing until you get to t ... ... 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 Changes for ... することに重点を置いています。 Common changes ¶ This section describes the changes between 0.96 and 1.0 that most users will need to make. Use Unicode ¶ Change string literals ( 'foo' ) into Unicode literals ( u'foo' ). Django now uses Unicode strings ... emove the core argument from your model fields. It is no longer necessary, since the equivalent functionality (part of inline editing ) is handled differently by the admin interface now. You don't have to worry about inline editing until you get to t ... ... p_*() methods on Field , below. The internals of template tags have changed somewhat; authors of custom template tags that need to store state (e.g. custom control flow tags) should ensure that their code follows the new rules for stateful template t ... vendors today are shipping Python 2.4 or newer as their default version. If you're still using Python 2.3, however, you'll need to stick to Django 1.1 until you can upgrade; per our support policy , Django 1.1 will continue to receive security suppor ... API and the template core machinery still accepts function-based loaders (builtin or third party) so there is no immediate need to modify your TEMPLATE_LOADERS setting in existing projects, things will keep working if you leave it untouched up to and ... ... p_*() methods on Field , below. The internals of template tags have changed somewhat; authors of custom template tags that need to store state (e.g. custom control flow tags) should ensure that their code follows the new rules for stateful template t ... vendors today are shipping Python 2.4 or newer as their default version. If you're still using Python 2.3, however, you'll need to stick to Django 1.1 until you can upgrade; per our support policy , Django 1.1 will continue to receive security suppor ... API and the template core machinery still accepts function-based loaders (builtin or third party) so there is no immediate need to modify your TEMPLATE_LOADERS setting in existing projects, things will keep working if you leave it untouched up to and ... ... ませんが、 このドキュメントをそれに応じて更新してください! オーバービュー ¶ There are three types of releases that you might need to make: Security releases: disclosing and fixing a vulnerability. This'll generally involve two or three simultaneous rel ... fic release(s) you are issuing, use the checklists app in the project admin . This populates a lot of boilerplate you will need for announcements, CVE publication, and hashes for commit messages. By using this app for preparing security issue metadat ... peer releasers can check your entries and consult them again in the future. See example checklist . Prerequisites ¶ You'll need a few things before getting started. If this is your first release, you'll need to coordinate with another releaser to get ... ... ませんが、 このドキュメントをそれに応じて更新してください! オーバービュー ¶ There are three types of releases that you might need to make: Security releases: disclosing and fixing a vulnerability. This'll generally involve two or three simultaneous rel ... fic release(s) you are issuing, use the checklists app in the project admin . This populates a lot of boilerplate you will need for announcements, CVE publication, and hashes for commit messages. By using this app for preparing security issue metadat ... peer releasers can check your entries and consult them again in the future. See example checklist . Prerequisites ¶ You'll need a few things before getting started. If this is your first release, you'll need to coordinate with another releaser to get ... ... vendors today are shipping Python 2.5 or newer as their default version. If you're still using Python 2.4, however, you'll need to stick to Django 1.3 until you can upgrade. Per our support policy , Django 1.3 will continue to receive security suppor ... d using the project name prefix (e.g. myproject.settings , ROOT_URLCONF = "myproject.urls" , etc.), the new manage.py will need to be moved one directory up, so it is outside the project package rather than adjacent to settings.py and urls.py . For i ... f the same code is imported inconsistently (some places with the project prefix, some places without it), the imports will need to be cleaned up when switching to the new manage.py . Custom project and app templates ¶ The startapp and startproject ma ... ... vendors today are shipping Python 2.5 or newer as their default version. If you're still using Python 2.4, however, you'll need to stick to Django 1.3 until you can upgrade. Per our support policy , Django 1.3 will continue to receive security suppor ... d using the project name prefix (e.g. myproject.settings , ROOT_URLCONF = "myproject.urls" , etc.), the new manage.py will need to be moved one directory up, so it is outside the project package rather than adjacent to settings.py and urls.py . For i ... f the same code is imported inconsistently (some places with the project prefix, some places without it), the imports will need to be cleaned up when switching to the new manage.py . Custom project and app templates ¶ The startapp and startproject ma ... ... l create a new directory "django", containing a clone of your GitHub repository. The rest of the git commands on this page need to be run within the cloned directory, so switch to it now: cd django Your GitHub repository will be called "origin" in Gi ... work of the merger. If you're uncomfortable with English, try at least to describe precisely what the commit does. If you need to do additional work on your branch, commit as often as necessary: git commit -m 'Added two more tests for edge cases.' P ... agraphs wrapped at 72 characters thereafter -- see the committing guidelines 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 mu ... ... l create a new directory "django", containing a clone of your GitHub repository. The rest of the git commands on this page need to be run within the cloned directory, so switch to it now: cd django Your GitHub repository will be called "origin" in Gi ... work of the merger. If you're uncomfortable with English, try at least to describe precisely what the commit does. If you need to do additional work on your branch, commit as often as necessary: git commit -m 'Added two more tests for edge cases.' P ... agraphs wrapped at 72 characters thereafter -- see the committing guidelines 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 mu ... 2026年10月08日