... covery, default_app_config is no longer needed. As a consequence, it's deprecated. See アプリケーションを設定する for full details. Customizing type of auto-created primary keys ¶ When defining a model, if no field in a model is defined with primary_key ... the primary key of existing auto-created through tables cannot be generated currently. See the DEFAULT_AUTO_FIELD docs for details on migrating such tables. Functional indexes ¶ The new *expressions positional argument of Index() enables creating functi ... w supports theming, and includes a dark theme that is enabled according to browser settings. See テーマのサポート for more details. ModelAdmin.autocomplete_fields now respects ForeignKey.to_field and ForeignKey.limit_choices_to when searching a related ... ... covery, default_app_config is no longer needed. As a consequence, it's deprecated. See アプリケーションを設定する for full details. Customizing type of auto-created primary keys ¶ When defining a model, if no field in a model is defined with primary_key ... the primary key of existing auto-created through tables cannot be generated currently. See the DEFAULT_AUTO_FIELD docs for details on migrating such tables. Functional indexes ¶ The new *expressions positional argument of Index() enables creating functi ... w supports theming, and includes a dark theme that is enabled according to browser settings. See テーマのサポート for more details. ModelAdmin.autocomplete_fields now respects ForeignKey.to_field and ForeignKey.limit_choices_to when searching a related ... ... st 1.1 unchanged, and you should need to make only minor changes for any 1.X release. See the API stability guide for full details. 後方互換性のない変更 ¶ Django 1.0 has a number of backwards-incompatible changes from Django 0.96. If you have apps writt ... umentation for the admin application is available online in the official Django documentation: See the admin reference for details Improved Unicode handling ¶ Django's internals have been refactored to use Unicode throughout; this drastically simplifies ... n provided to ease interoperability with third-party libraries and systems which may or may not handle Unicode gracefully. Details are available in Django's Unicode-handling documentation. 詳しくは Unicode データ を参照。 改善された ORM ¶ Django's objec ... ... st 1.1 unchanged, and you should need to make only minor changes for any 1.X release. See the API stability guide for full details. 後方互換性のない変更 ¶ Django 1.0 has a number of backwards-incompatible changes from Django 0.96. If you have apps writt ... umentation for the admin application is available online in the official Django documentation: See the admin reference for details Improved Unicode handling ¶ Django's internals have been refactored to use Unicode throughout; this drastically simplifies ... n provided to ease interoperability with third-party libraries and systems which may or may not handle Unicode gracefully. Details are available in Django's Unicode-handling documentation. 詳しくは Unicode データ を参照。 改善された ORM ¶ Django's objec ... ... は、多くの場合 2 つ前のバージョンのリリースノートで見つけることができます。 2028 ¶ See the Django 6.0 release notes for more details on these changes. The serialize keyword argument of BaseDatabaseCreation.create_test_db() will be removed. The django.cont ... ers() and django.core.mail.message.sanitize_address() functions will be removed. See the Django 6.1 release notes for more details on these changes. Calling QuerySet.values_list() with flat=True and no field name will raise TypeError . The use of None w ... ethods that do not accept the fetch_mode keyword argument will be removed. 6.1 ¶ See the Django 5.2 release notes for more details on these changes. The all keyword argument of django.contrib.staticfiles.finders.find() will be removed. Fallbacks to requ ... ... は、多くの場合 2 つ前のバージョンのリリースノートで見つけることができます。 2028 ¶ See the Django 6.0 release notes for more details on these changes. The serialize keyword argument of BaseDatabaseCreation.create_test_db() will be removed. The django.cont ... ers() and django.core.mail.message.sanitize_address() functions will be removed. See the Django 6.1 release notes for more details on these changes. Calling QuerySet.values_list() with flat=True and no field name will raise TypeError . The use of None w ... ethods that do not accept the fetch_mode keyword argument will be removed. 6.1 ¶ See the Django 5.2 release notes for more details on these changes. The all keyword argument of django.contrib.staticfiles.finders.find() will be removed. Fallbacks to requ ... ... tion ¶ Django 1.1 runs tests inside a transaction, allowing better test performance (see test performance improvements for details). This change is slightly backwards incompatible if existing tests need to test transactional behavior, if they rely on in ... raded to a DeprecationWarning , which will be displayed loudly. Django 1.3 will remove AdminSite.root() entirely. For more details on our deprecation policies and strategy, see Django のリリースプロセス . Django 1.1 の新機能 ¶ Quite a bit: since Django ... ery and can traverse relationships to refer to fields on related models. This is implemented in the new F object; for full details, including examples, consult the F expressions documentation . Model improvements ¶ A number of features have been added t ... ... tion ¶ Django 1.1 runs tests inside a transaction, allowing better test performance (see test performance improvements for details). This change is slightly backwards incompatible if existing tests need to test transactional behavior, if they rely on in ... raded to a DeprecationWarning , which will be displayed loudly. Django 1.3 will remove AdminSite.root() entirely. For more details on our deprecation policies and strategy, see Django のリリースプロセス . Django 1.1 の新機能 ¶ Quite a bit: since Django ... ery and can traverse relationships to refer to fields on related models. This is implemented in the new F object; for full details, including examples, consult the F expressions documentation . Model improvements ¶ A number of features have been added t ... ... e basis for reusable applications that can be easily extended. See the documentation on class-based generic views for more details. There is also a document to help you convert your function-based generic views to class-based views . ロギング ¶ Django 1 ... HTTP 500 server error are now handled as a logging activity. See the documentation on Django's logging interface for more details. Extended static files handling ¶ Django 1.3 ships with a new contrib app -- django.contrib.staticfiles -- to help develop ... tories listed in STATICFILES_DIRS , and will be served at STATIC_URL . See the reference documentation of the app for more details or learn how to manage static files . unittest2 のサポート ¶ Python 2.7 では unittest ライブラリに大きな変更が加えられ、非 ... ... e basis for reusable applications that can be easily extended. See the documentation on class-based generic views for more details. There is also a document to help you convert your function-based generic views to class-based views . ロギング ¶ Django 1 ... HTTP 500 server error are now handled as a logging activity. See the documentation on Django's logging interface for more details. Extended static files handling ¶ Django 1.3 ships with a new contrib app -- django.contrib.staticfiles -- to help develop ... tories listed in STATICFILES_DIRS , and will be served at STATIC_URL . See the reference documentation of the app for more details or learn how to manage static files . unittest2 のサポート ¶ Python 2.7 では unittest ライブラリに大きな変更が加えられ、非 ... 2026年10月08日