... e changes you'll want to be aware of when upgrading from Django 1.3 or older versions. We've also dropped some features, which are detailed in our deprecation plan , and we've begun the deprecation process fo ... , and simple clickjacking protection . An updated default project layout and manage.py that removes the "magic" from prior versions. And for those who don't like the new layout, you can use custom project and app templates instead! Support for in-browser ... s with previous releases, Django 1.4 ships with some minor backwards incompatible changes ; people upgrading from previous versions of Django should read that list carefully. Python バージョン間の互換性 ¶ Django 1.4 has dropped support for Python 2.4. Py ... ... within the same project. Learn more about the new features in the topic guide and check the upgrade instructions in older versions of the documentation. Security enhancements ¶ サードパーティライブラリである django-secure の機能の一部が Django に統合され ... tion to define a default related name for all relational fields of a model. Pickling models and querysets across different versions of Django isn't officially supported (it may work, but there's no guarantee). An extra variable that specifies the current ... s compatible by simply setting the args class variable. However, if you don't have to keep compatibility with older Django versions, it's better to implement the new add_arguments() method as described in カスタム django-admin コマンドの作り方 . Custom t ... ... within the same project. Learn more about the new features in the topic guide and check the upgrade instructions in older versions of the documentation. Security enhancements ¶ サードパーティライブラリである django-secure の機能の一部が Django に統合され ... tion to define a default related name for all relational fields of a model. Pickling models and querysets across different versions of Django isn't officially supported (it may work, but there's no guarantee). An extra variable that specifies the current ... s compatible by simply setting the args class variable. However, if you don't have to keep compatibility with older Django versions, it's better to implement the new add_arguments() method as described in カスタム django-admin コマンドの作り方 . Custom t ... ... e changes you'll want to be aware of when upgrading from Django 1.3 or older versions. We've also dropped some features, which are detailed in our deprecation plan , and we've begun the deprecation process fo ... , and simple clickjacking protection . An updated default project layout and manage.py that removes the "magic" from prior versions. And for those who don't like the new layout, you can use custom project and app templates instead! Support for in-browser ... s with previous releases, Django 1.4 ships with some minor backwards incompatible changes ; people upgrading from previous versions of Django should read that list carefully. Python バージョン間の互換性 ¶ Django 1.4 has dropped support for Python 2.4. Py ... ... atures , as well as some backwards incompatible changes you'll want to be aware of when upgrading from Django 1.5 or older versions. We've also dropped some features, which are detailed in our deprecation plan , and we've begun the deprecation process fo ... l reliably be called. The validate_max parameter was added to BaseFormSet and formset_factory() , and ModelForm and inline versions of the same. The behavior of validation for formsets with max_num was clarified. The previously undocumented behavior that ... lated to savepoints, and adjust the expected number of queries accordingly. Autocommit option for PostgreSQL ¶ In previous versions, database-level autocommit was only an option for PostgreSQL, and it was disabled by default. This option is now ignored a ... ... support. Older versions of 1.4 would silently build a broken wheel when installed with those versions of pip. Denial-of-service possibility in log ... へ Django 1.5 リリースノート 次のトピックへ Django 1.4.21 リリースノート 関連キーワード session records fixes support wheel versions logout view filling store contrib create empty backends flush リリースノート August security issue also disabling Older si ... ... atures , as well as some backwards incompatible changes you'll want to be aware of when upgrading from Django 1.5 or older versions. We've also dropped some features, which are detailed in our deprecation plan , and we've begun the deprecation process fo ... l reliably be called. The validate_max parameter was added to BaseFormSet and formset_factory() , and ModelForm and inline versions of the same. The behavior of validation for formsets with max_num was clarified. The previously undocumented behavior that ... lated to savepoints, and adjust the expected number of queries accordingly. Autocommit option for PostgreSQL ¶ In previous versions, database-level autocommit was only an option for PostgreSQL, and it was disabled by default. This option is now ignored a ... ... support. Older versions of 1.4 would silently build a broken wheel when installed with those versions of pip. Denial-of-service possibility in log ... 5 リリースノート 次のトピックへ Django 1.4.21 リリースノート 関連キーワード session records Django fixes support pip wheel versions logout view filling store contrib create new empty backends flush リリースノート August 関連するページ Django 1.7.10 リリー ... ... tests on Oracle ¶ When running tests with an Oracle database, Django creates a temporary database user. In older versions, if a password isn't manually specified in the database settings TEST dictionary, a hardcoded password is used. This could ... nection). A randomly generated password is now used for each test run. DNS rebinding vulnerability when DEBUG=True ¶ Older versions of Django don't validate the Host header against settings.ALLOWED_HOSTS when settings.DEBUG=True . This makes them vulnera ... 5 リリースノート 関連キーワード database settings password user attacker connect production hardcoded running tests Oracle versions used rebinding developers development localhost リリースノート November fixes security issues User created creates クイック ... ... o will set a Vary: Cookie header to ensure caches do not serve cached data to requests from other sessions. However, older versions of Internet Explorer (most likely only Internet Explorer 6, and Internet Explorer 7 if run on Windows XP or Windows Server ... eader if the request was made by Internet Explorer. To remedy this, the special behavior for these older Internet Explorer versions has been removed, and the Vary header is no longer stripped from the response. In addition, modifications to the Cache-Con ... Ls user correctly serve session requests Vary these validate malformed security issues store private caches sessions older versions Windows handle remedy removed redirect クイック検索 Last update: 2026年10月09日 « previous | up | next » ... 2026年10月08日