... res, backwards incompatibilities, and deprecated features in the 1.1 branch, see the Django 1.1 リリースノート . Backwards incompatible changes ¶ Restricted filters in admin interface ¶ The Django administrative interface, django.contrib.admin , supports fil ... ve been explicitly allowed by the application developer using the preexisting mechanism mentioned above. This is backwards-incompatible for any users relying on the prior ability to insert arbitrary lookups. 目次 Django 1.1.3 リリースノート Backwards incompa ... .1.2 リリースノート 関連キーワード admin backwards fields lookup arguments querystring model リリースノート using features incompatible filters interface contrib filtering database relationships specify supported ability user sufficient knowledge structure a ... ... res, backwards incompatibilities, and deprecated features in the 1.1 branch, see the Django 1.1 リリースノート . Backwards incompatible changes ¶ Restricted filters in admin interface ¶ The Django administrative interface, django.contrib.admin , supports fil ... ve been explicitly allowed by the application developer using the preexisting mechanism mentioned above. This is backwards-incompatible for any users relying on the prior ability to insert arbitrary lookups. 目次 Django 1.1.3 リリースノート Backwards incompa ... ースノート 関連キーワード Django admin backwards fields lookup arguments querystring model リリースノート using new features incompatible filters interface django contrib filtering database relationships 関連するページ Django 1.2.4 リリースノート Django 1.1 リ ... ... upgrade path from Django 1.0. Backwards-incompatible changes in 1.1 ¶ Django has a policy of API stability . This means that, in general, code you develop against Django 1.0 s ... hould continue to work against 1.1 unchanged. However, we do sometimes make backwards-incompatible changes if they're necessary to resolve bugs, and there are a handful of such (minor) changes between Django 1.0 and Djang ... generate database constraint names so that names are consistent regardless of machine word size. This change is backwards incompatible for some users. If you are using a 32-bit platform, you're off the hook; you'll observe no differences as a result of this ... ... upgrade path from Django 1.0. Backwards-incompatible changes in 1.1 ¶ Django has a policy of API stability . This means that, in general, code you develop against Django 1.0 s ... hould continue to work against 1.1 unchanged. However, we do sometimes make backwards-incompatible changes if they're necessary to resolve bugs, and there are a handful of such (minor) changes between Django 1.0 and Djang ... generate database constraint names so that names are consistent regardless of machine word size. This change is backwards incompatible for some users. If you are using a 32-bit platform, you're off the hook; you'll observe no differences as a result of this ... ... res, backwards incompatibilities, and deprecated features in the 1.1 branch, see the Django 1.1 リリースノート . Backwards incompatible changes ¶ CSRF exception for AJAX requests ¶ Django includes a CSRF-protection mechanism, which makes use of a token inser ... ngo will now apply full CSRF validation to all requests, regardless of apparent AJAX origin. This is technically backwards-incompatible, but the security risks have been judged to outweigh the compatibility concerns in this case. Additionally, Django will no ... go, as the exact code necessary is different for some older versions of Django. 目次 Django 1.1.4 リリースノート Backwards incompatible changes CSRF exception for AJAX requests 前のトピックへ Django 1.2 リリースノート 次のトピックへ Django 1.1.3 リリースノー ... ... res, backwards incompatibilities, and deprecated features in the 1.2 branch, see the Django 1.2 リリースノート . Backwards incompatible changes ¶ Restricted filters in admin interface ¶ The Django administrative interface, django.contrib.admin , supports fil ... ve been explicitly allowed by the application developer using the preexisting mechanism mentioned above. This is backwards-incompatible for any users relying on the prior ability to insert arbitrary lookups. One new feature ¶ Ordinarily, a point release woul ... ng the Django test suite with runtests.py and using spatial database backends . 目次 Django 1.2.4 リリースノート Backwards incompatible changes Restricted filters in admin interface One new feature GeoDjango 前のトピックへ Django 1.2.5 リリースノート 次のトピ ... ... wards incompatible change that hopefully doesn't affect any users. Security issue: User with "change" but not "add" permission can create obj ... prevented that form submission from raising a "Permission Denied" error for users without the "add" permission. Backwards incompatible change: .py-tpl files rewritten in project/app templates ¶ The addition of some Django template language syntax to the def ... curity issue: User with "change" but not "add" permission can create objects for ModelAdmin 's with save_as=True Backwards incompatible change: .py-tpl files rewritten in project/app templates バグ修正 前のトピックへ Django 1.9.3 リリースノート 次のトピックへ ... ... ere have been a few small backwards-incompatible changes since 0.95, but the upgrade process should be fairly simple and should not require major changes to existing appli ... cations. However, we're also releasing 0.96 now because we have a set of backwards-incompatible changes scheduled for the near future. Once completed, they will involve some code changes for application developers, so ... e current django.forms to django.oldforms . This allows you to upgrade your code now rather than waiting for the backwards-incompatible change and rushing to fix your code after the fact. Just change your import statements like this: from django import forms ... ... res, backwards incompatibilities, and deprecated features in the 1.1 branch, see the Django 1.1 リリースノート . Backwards incompatible changes ¶ CSRF exception for AJAX requests ¶ Django includes a CSRF-protection mechanism, which makes use of a token inser ... ngo will now apply full CSRF validation to all requests, regardless of apparent AJAX origin. This is technically backwards-incompatible, but the security risks have been judged to outweigh the compatibility concerns in this case. Additionally, Django will no ... go, as the exact code necessary is different for some older versions of Django. 目次 Django 1.1.4 リリースノート Backwards incompatible changes CSRF exception for AJAX requests 前のトピックへ Django 1.2 リリースノート 次のトピックへ Django 1.1.3 リリースノー ... ... tible manner per our API stability policy . However, as with previous releases, Django 1.5 ships with some minor backwards incompatible changes ; people upgrading from previous versions of Django should read that list carefully. One deprecated feature worth ... rs can now be customized per-request thanks to the new django.contrib.admin.ModelAdmin.get_list_filter() method. Backwards incompatible changes in 1.5 ¶ 警告 In addition to the changes outlined in this section, be sure to review the deprecation plan for any ... f you haven't updated your code within the deprecation timeline for a given feature, its removal may appear as a backwards incompatible change. ALLOWED_HOSTS required in production ¶ The new ALLOWED_HOSTS setting validates the request's Host header and prote ... 2026年10月08日