... ated features in the 1.1 branch, see the Django 1.1 リリースノート . Backwards-incompatible changes in 1.1.2 ¶ Test runner exit status code ¶ The exit status code of the test runners ( tests/runtests.py and python manage.py test ) no longer represent ... s the number of failed tests, since a failure of 256 or more tests resulted in a wrong exit status code. The exit status code for the test runner is now 0 for success (no failing tests) and 1 for any number of test ... e template will work with Django 1.2. 目次 Django 1.1.2 リリースノート Backwards-incompatible changes in 1.1.2 Test runner exit status code Cookie encoding One new feature 前のトピックへ Django 1.1.3 リリースノート 次のトピックへ Django 1.1 リリースノ ... ... ated features in the 1.1 branch, see the Django 1.1 リリースノート . Backwards-incompatible changes in 1.1.2 ¶ Test runner exit status code ¶ The exit status code of the test runners ( tests/runtests.py and python manage.py test ) no longer represent ... s the number of failed tests, since a failure of 256 or more tests resulted in a wrong exit status code. The exit status code for the test runner is now 0 for success (no failing tests) and 1 for any number of test ... e template will work with Django 1.2. 目次 Django 1.1.2 リリースノート Backwards-incompatible changes in 1.1.2 Test runner exit status code Cookie encoding One new feature 前のトピックへ Django 1.1.3 リリースノート 次のトピックへ Django 1.1 リリースノ ... ... used to run Django's own test suite now support a --failfast option. When specified, this option causes the test runner to exit after encountering a failure instead of continuing with the test run. In addition, the handling of Ctrl-C during a test ru ... n has been improved to trigger a graceful exit from the test run that reports details of the tests that were run before the interruption. BigIntegerField ¶ Models can no ... er __dict__ to obtain a list of fields, you must now be prepared to handle or filter out the _state attribute. Test runner exit status code ¶ The exit status code of the test runners ( tests/runtests.py and python manage.py test ) no longer represent ... ... used to run Django's own test suite now support a --failfast option. When specified, this option causes the test runner to exit after encountering a failure instead of continuing with the test run. In addition, the handling of Ctrl-C during a test ru ... n has been improved to trigger a graceful exit from the test run that reports details of the tests that were run before the interruption. BigIntegerField ¶ Models can no ... er __dict__ to obtain a list of fields, you must now be prepared to handle or filter out the _state attribute. Test runner exit status code ¶ The exit status code of the test runners ( tests/runtests.py and python manage.py test ) no longer represent ... ... mand.handle() method. The new check --fail-level option allows specifying the message level that will cause the command to exit with a non-zero status. The new makemigrations --check option makes the command exit with a non-zero status when model cha ... python to force use of the "plain" Python interpreter. The new shell --command option lets you run a command as Django and exit, instead of opening the interactive shell. Added a warning to dumpdata if a proxy model is specified (which results in no ... g can be silenced by setting silence_use_for_related_fields_deprecation=True on the manager. その他 ¶ The makemigrations --exit option is deprecated in favor of the makemigrations --check option. django.utils.functional.allow_lazy() is deprecated in ... ... mand.handle() method. The new check --fail-level option allows specifying the message level that will cause the command to exit with a non-zero status. The new makemigrations --check option makes the command exit with a non-zero status when model cha ... python to force use of the "plain" Python interpreter. The new shell --command option lets you run a command as Django and exit, instead of opening the interactive shell. Added a warning to dumpdata if a proxy model is specified (which results in no ... g can be silenced by setting silence_use_for_related_fields_deprecation=True on the manager. その他 ¶ The makemigrations --exit option is deprecated in favor of the makemigrations --check option. django.utils.functional.allow_lazy() is deprecated in ... ... する際に一度だけ入力を求められます。それを忘れないようにしてください! インストーラーが完了すると、 "Launch Stack Builder at exit?" （スタックビルダーを終了時に起動しますか?）という質問が表示されます。これは、 PostGIS をインストールするために必要ですの ... ext and accepting the license agreements, the packages will be automatically downloaded and installed, after which you may exit the installer. Windows 環境変数の変更 ¶ In order to use GeoDjango, you will need to add your OSGeo4W directories to your W ... ... el.check() is unreachable ( #23615 ). Made the Oracle test database creation drop the test user in the event of an unclean exit of a previous test run ( #23649 ). Fixed makemigrations to detect changes to Meta.db_table ( #23629 ). Fixed a regression ... ... する際に一度だけ入力を求められます。それを忘れないようにしてください! インストーラーが完了すると、 "Launch Stack Builder at exit?" （スタックビルダーを終了時に起動しますか?）という質問が表示されます。これは、 PostGIS をインストールするために必要ですの ... ext and accepting the license agreements, the packages will be automatically downloaded and installed, after which you may exit the installer. Windows 環境変数の変更 ¶ In order to use GeoDjango, you will need to add your OSGeo4W directories to your W ... ... el.check() is unreachable ( #23615 ). Made the Oracle test database creation drop the test user in the event of an unclean exit of a previous test run ( #23649 ). Fixed makemigrations to detect changes to Meta.db_table ( #23629 ). Fixed a regression ... 2026年10月08日