... custom project and app templates instead! Support for in-browser testing frameworks (like Selenium ). ... and a whole lot more; see below ! Wherever possible we try to introduce new features in a backwards-compatible manner per our API stability pol ... "really means". This can cause all sorts of subtle timezone-related bugs. In Django 1.4, you can now switch Django into a more correct, time-zone aware mode. In this mode, Django stores date and time information in UTC in the database, uses time-zon ... . The new django.test.LiveServerTestCase base class lets you test the interactions between your site's front and back ends more comprehensively. See the documentation for more details and concrete examples. Updated default project layout and manage.p ... ... custom project and app templates instead! Support for in-browser testing frameworks (like Selenium ). ... and a whole lot more; see below ! Wherever possible we try to introduce new features in a backwards-compatible manner per our API stability pol ... "really means". This can cause all sorts of subtle timezone-related bugs. In Django 1.4, you can now switch Django into a more correct, time-zone aware mode. In this mode, Django stores date and time information in UTC in the database, uses time-zon ... . The new django.test.LiveServerTestCase base class lets you test the interactions between your site's front and back ends more comprehensively. See the documentation for more details and concrete examples. Updated default project layout and manage.p ... ... a consequence of decisions made in the early days of Django, prior to its open-source release. It's now possible to write more natural, Pythonic code that works as expected, and there's less "black magic" happening behind the scenes. Aside from that ... , etc., to improve developers' quality of life. The new features and changes introduced in 0.95 include: Django now uses a more consistent and natural filtering interface for retrieving objects from the database. User-defined models, functions and co ... wn. Previously, the framework required that a database be configured, regardless of whether you actually used it. It's now more explicit and natural to override save() and delete() methods on models, rather than needing to hook into the pre_save() an ... ... a consequence of decisions made in the early days of Django, prior to its open-source release. It's now possible to write more natural, Pythonic code that works as expected, and there's less "black magic" happening behind the scenes. Aside from that ... , etc., to improve developers' quality of life. The new features and changes introduced in 0.95 include: Django now uses a more consistent and natural filtering interface for retrieving objects from the database. User-defined models, functions and co ... wn. Previously, the framework required that a database be configured, regardless of whether you actually used it. It's now more explicit and natural to override save() and delete() methods on models, rather than needing to hook into the pre_save() an ... ... port for streaming responses via the new StreamingHttpResponse response class. GeoDjango now supports PostGIS 2.0. ... and more; see below . Wherever possible we try to introduce new features in a backwards-compatible manner per our API stability pol ... kend (depends on MySQLdb) ImageField (depends on PIL) LiveServerTestCase (depends on Selenium WebDriver) Further, Django's more than a web framework; it's an ecosystem of pluggable components. At this point, very few third-party applications have bee ... ¶ In Django 1.5, you can now use your own model as the store for user-related data. If your project needs a username with more than 30 characters, or if you want to store user's names in a format other than first name/last name, or you want to put c ... ... w_syncdb methods will still work, but that method name is deprecated and you should change it as soon as possible (nothing more than renaming is required). initial_data fixtures are no longer loaded for apps with migrations; if you want to load initi ... signed correctly to models even when they're defined outside of models.py . You don't have to set app_label explicitly any more. It is possible to omit models.py entirely if an application doesn't have any models. Applications can be relabeled with t ... prefetched relation, or prefetching the same relation multiple times with different querysets. See prefetch_related() for more details. Admin shortcuts support time zones ¶ The "today" and "now" shortcuts next to date and time input widgets in the a ... ... w_syncdb methods will still work, but that method name is deprecated and you should change it as soon as possible (nothing more than renaming is required). initial_data fixtures are no longer loaded for apps with migrations; if you want to load initi ... signed correctly to models even when they're defined outside of models.py . You don't have to set app_label explicitly any more. It is possible to omit models.py entirely if an application doesn't have any models. Applications can be relabeled with t ... prefetched relation, or prefetching the same relation multiple times with different querysets. See prefetch_related() for more details. Admin shortcuts support time zones ¶ The "today" and "now" shortcuts next to date and time input widgets in the a ... ... port for streaming responses via the new StreamingHttpResponse response class. GeoDjango now supports PostGIS 2.0. ... and more; see below . Wherever possible we try to introduce new features in a backwards-compatible manner per our API stability pol ... kend (depends on MySQLdb) ImageField (depends on PIL) LiveServerTestCase (depends on Selenium WebDriver) Further, Django's more than a web framework; it's an ecosystem of pluggable components. At this point, very few third-party applications have bee ... ¶ In Django 1.5, you can now use your own model as the store for user-related data. If your project needs a username with more than 30 characters, or if you want to store user's names in a format other than first name/last name, or you want to put c ... ... 詳細は、多くの場合 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 dja ... _headers() 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 o ... b() methods 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 ... ... plicit primary key can now be controlled via the DEFAULT_AUTO_FIELD setting and AppConfig.default_auto_field attribute. No more needing to override primary keys in all models. Maintaining the historical behavior, the default value for DEFAULT_AUTO_FI ... n instead after assigning the required attributes to the method. Using decorators has the advantage that these options are more discoverable as they can be suggested by completion utilities in code editors. They are merely a convenience and still set ... in now 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 ... 2026年10月08日