... ced maximum number of forms (1000 by default, though it can be set higher via the max_num formset factory argument). Admin history view information leakage ¶ In previous versions of Django, an admin user without change permission on a model could still ... view the Unicode representation of instances via their admin history log. Django 1.3.6 now limits the admin history log view for an object to users with change permission for that model. 目次 ... Django 1.3.6 リリースノート Host header poisoning XML deserialization Formset memory exhaustion Admin history view information leakage 前のトピックへ Django 1.3.7 リリースノート 次のトピックへ Django 1.3.5 リリースノート 関連キーワー ... ... ced maximum number of forms (1000 by default, though it can be set higher via the max_num formset factory argument). Admin history view information leakage ¶ In previous versions of Django, an admin user without change permission on a model could still ... view the Unicode representation of instances via their admin history log. Django 1.3.6 now limits the admin history log view for an object to users with change permission for that model. 目次 ... Django 1.3.6 リリースノート Host header poisoning XML deserialization Formset memory exhaustion Admin history view information leakage 前のトピックへ Django 1.3.7 リリースノート 次のトピックへ Django 1.3.5 リリースノート 関連キーワー ... ... ced maximum number of forms (1000 by default, though it can be set higher via the max_num formset factory argument). Admin history view information leakage ¶ In previous versions of Django, an admin user without change permission on a model could still ... view the Unicode representation of instances via their admin history log. Django 1.4.4 now limits the admin history log view for an object to users with change permission for that model. Othe ... ents and fixes. 目次 Django 1.4.4 リリースノート Host header poisoning XML deserialization Formset memory exhaustion Admin history view information leakage Other bugfixes and changes 前のトピックへ Django 1.4.5 リリースノート 次のトピックへ Django 1.4.3 ... ... ced maximum number of forms (1000 by default, though it can be set higher via the max_num formset factory argument). Admin history view information leakage ¶ In previous versions of Django, an admin user without change permission on a model could still ... view the Unicode representation of instances via their admin history log. Django 1.4.4 now limits the admin history log view for an object to users with change permission for that model. Othe ... ents and fixes. 目次 Django 1.4.4 リリースノート Host header poisoning XML deserialization Formset memory exhaustion Admin history view information leakage Other bugfixes and changes 前のトピックへ Django 1.4.5 リリースノート 次のトピックへ Django 1.4.3 ... ... a link to your branch. Note that the above branch is called a "topic branch" in Git parlance. You are free to rewrite the history of this branch, by using git rebase for example. Other people shouldn't base their work on such a branch, because their cl ... rupt when you edit commits. There are also "public branches". These are branches other people are supposed to fork, so the history of these branches should never change. Good examples of public branches are the main and stable/A.B.x branches in the djan ... two commits, the "Fixed #xxxxx -- ..." commit and the "Added two more tests ..." commit. We do not want to have the entire history of your working process in your repository. Your commit "Added two more tests" would be unhelpful noise. Instead, we would ... ... a link to your branch. Note that the above branch is called a "topic branch" in Git parlance. You are free to rewrite the history of this branch, by using git rebase for example. Other people shouldn't base their work on such a branch, because their cl ... rupt when you edit commits. There are also "public branches". These are branches other people are supposed to fork, so the history of these branches should never change. Good examples of public branches are the main and stable/A.B.x branches in the djan ... two commits, the "Fixed #xxxxx -- ..." commit and the "Added two more tests ..." commit. We do not want to have the entire history of your working process in your repository. Your commit "Added two more tests" would be unhelpful noise. Instead, we would ... ... ficial branches in the source code repository. The following section is mostly useful if you're exploring the repository's history, for example if you're trying to understand how some features were designed. Feature-development branches tend by their na ... re closed, but whose code was never merged into Django, and the features they aimed to implement were never finished: full-history generic-auth multiple-db-support per-object-permissions schema-evolution schema-evolution-ng search-api sqlalchemy Finally ... ... rror ( #27271 ). Fixed a regression where unchanged localized date/time fields were listed as changed in the admin's model history messages ( #27302 ). 目次 Django 1.10.2 リリースノート バグ修正 前のトピックへ Django 1.10.3 リリースノート 次のトピックへ ... ... ficial branches in the source code repository. The following section is mostly useful if you're exploring the repository's history, for example if you're trying to understand how some features were designed. Feature-development branches tend by their na ... re closed, but whose code was never merged into Django, and the features they aimed to implement were never finished: full-history generic-auth multiple-db-support per-object-permissions schema-evolution schema-evolution-ng search-api sqlalchemy Finally ... ... rror ( #27271 ). Fixed a regression where unchanged localized date/time fields were listed as changed in the admin's model history messages ( #27302 ). 目次 Django 1.10.2 リリースノート バグ修正 前のトピックへ Django 1.10.3 リリースノート 次のトピックへ ... 2026年10月08日