... t() if the SITE_ID setting is not defined. The default Site created when running migrate now respects the SITE_ID setting (instead of always using pk=1 ). キャッシュ ¶ The incr() method of the django.core.cache.backends.locmem.LocMemCache backend is now ... ady creates them automatically. The Oracle backend no longer defines the connection_persists_old_columns feature as True . Instead, Oracle will now include a cache busting clause when getting the description of a table. E メール ¶ Email backends now sup ... SSL certificate authority setting ( --ssl-ca ). The new makemigrations --name allows giving the migration(s) a custom name instead of a generated one. The loaddata command now prevents repeated fixture loading. If FIXTURE_DIRS contains duplicates or a d ... ... t() if the SITE_ID setting is not defined. The default Site created when running migrate now respects the SITE_ID setting (instead of always using pk=1 ). キャッシュ ¶ The incr() method of the django.core.cache.backends.locmem.LocMemCache backend is now ... ady creates them automatically. The Oracle backend no longer defines the connection_persists_old_columns feature as True . Instead, Oracle will now include a cache busting clause when getting the description of a table. E メール ¶ Email backends now sup ... SSL certificate authority setting ( --ssl-ca ). The new makemigrations --name allows giving the migration(s) a custom name instead of a generated one. The loaddata command now prevents repeated fixture loading. If FIXTURE_DIRS contains duplicates or a d ... ... core.mail APIs will no longer accept certain parameters as positional arguments. These must be passed as keyword arguments instead. Support for passing Python's legacy email email.mime.base.MIMEBase object to EmailMessage.attach() (or including one in t ... f None when querying a JSONField top-level value will compile to SQL IS NULL . Use JSONNull to query for a JSON null value instead. The django.db.models.fields.BLANK_CHOICE_DASH constant will be removed. The USE_BLANK_CHOICE_DASH transitional setting wi ... king or indexing the dictionary values of the ModelAdmin.get_actions() return value will be removed. Use Action attributes instead. Support for overriding ModelAdmin.get_action_choices() without the new action_location parameter will be removed. The dja ... ... core.mail APIs will no longer accept certain parameters as positional arguments. These must be passed as keyword arguments instead. Support for passing Python's legacy email email.mime.base.MIMEBase object to EmailMessage.attach() (or including one in t ... f None when querying a JSONField top-level value will compile to SQL IS NULL . Use JSONNull to query for a JSON null value instead. The django.db.models.fields.BLANK_CHOICE_DASH constant will be removed. The USE_BLANK_CHOICE_DASH transitional setting wi ... king or indexing the dictionary values of the ModelAdmin.get_actions() return value will be removed. Use Action attributes instead. Support for overriding ModelAdmin.get_action_choices() without the new action_location parameter will be removed. The dja ... ... dependencies satisfied under Python 3. Thus, we're recommending that Django 1.5 not be used in production under Python 3. Instead, use this opportunity to begin porting applications to Python 3. If you're an author of a pluggable component, we encourag ... onsistency with the design of the other generic views, TemplateView no longer passes a params dictionary into the context, instead passing the variables from the URLconf directly into the context. Non-form data in HTTP requests ¶ request.POST will no lo ... uest.POST attribute. Developers wishing to access the raw POST data for these cases, should use the request.body attribute instead. request_finished signal ¶ Django used to send the request_finished signal as soon as the view function returned a respons ... ... dependencies satisfied under Python 3. Thus, we're recommending that Django 1.5 not be used in production under Python 3. Instead, use this opportunity to begin porting applications to Python 3. If you're an author of a pluggable component, we encourag ... onsistency with the design of the other generic views, TemplateView no longer passes a params dictionary into the context, instead passing the variables from the URLconf directly into the context. Non-form data in HTTP requests ¶ request.POST will no lo ... uest.POST attribute. Developers wishing to access the raw POST data for these cases, should use the request.body attribute instead. request_finished signal ¶ Django used to send the request_finished signal as soon as the view function returned a respons ... ... d fields syntax was quite confusing, and has been simplified. The old syntax still works, but you'll need to use fieldsets instead. Old (0.96): class ModelOne ( models . Model ): ... class Admin : fields = (( None , { "fields" : ( "foo" , "bar" )}),) cl ... atterns ( "" , ( r "^admin/(.*)" , admin . site . root ), # ... the rest of your URLs here ... ) ビュー ¶ Use django.forms instead of newforms ¶ Replace django.newforms with django.forms -- Django 1.0 renamed the newforms module (introduced in 0.96) to ... attributes only make sense for ImageField fields. More details can be found in the model API documentation. Use Paginator instead of ObjectPaginator ¶ The ObjectPaginator in 0.96 has been removed and replaced with an improved version, django.core.pagin ... ... d fields syntax was quite confusing, and has been simplified. The old syntax still works, but you'll need to use fieldsets instead. Old (0.96): class ModelOne ( models . Model ): ... class Admin : fields = (( None , { "fields" : ( "foo" , "bar" )}),) cl ... atterns ( "" , ( r "^admin/(.*)" , admin . site . root ), # ... the rest of your URLs here ... ) ビュー ¶ Use django.forms instead of newforms ¶ Replace django.newforms with django.forms -- Django 1.0 renamed the newforms module (introduced in 0.96) to ... attributes only make sense for ImageField fields. More details can be found in the model API documentation. Use Paginator instead of ObjectPaginator ¶ The ObjectPaginator in 0.96 has been removed and replaced with an improved version, django.core.pagin ... ... tor when needing to specify attributes on the custom method. Prior to this it was necessary to use the property() function instead after assigning the required attributes to the method. Using decorators has the advantage that these options are more disc ... page links in a template. Request と Response ¶ Response headers are now stored in HttpResponse.headers . This can be used instead of the original dict-like interface of HttpResponse objects. Both interfaces will continue to be supported. See ヘッダーフ ... abaseFeatures.collate_as_index_expression to True . django.contrib.admin ¶ Pagination links in the admin are now 1-indexed instead of 0-indexed, i.e. the query string for the first page is ?p=1 instead of ?p=0 . The new admin catch-all view will break U ... ... tor when needing to specify attributes on the custom method. Prior to this it was necessary to use the property() function instead after assigning the required attributes to the method. Using decorators has the advantage that these options are more disc ... page links in a template. Request と Response ¶ Response headers are now stored in HttpResponse.headers . This can be used instead of the original dict-like interface of HttpResponse objects. Both interfaces will continue to be supported. See ヘッダーフ ... abaseFeatures.collate_as_index_expression to True . django.contrib.admin ¶ Pagination links in the admin are now 1-indexed instead of 0-indexed, i.e. the query string for the first page is ?p=1 instead of ?p=0 . The new admin catch-all view will break U ... 2026年10月08日