per page, with , order by , clip by
Results of 1 - 10 of about 120 for still (0.007 sec.)
Django 1.7 リリースノート — Django 6.1 ドキュメント 10692
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.7 リリースノート ¶ September 2, 2014 Django 1.7 へようこそ! このリリースノートでは、 バージョン 1.7 の新機能 と、Django 1.6 以前からアップグ ... Django users, as most operating-system vendors today are shipping Python 2.7 or newer as their default version. If you're still using Python 2.6, however, you'll need to stick to Django 1.6 until you can upgrade your Python version. Per our support p ... but a few of the key features are: syncdb has been deprecated and replaced by migrate . Don't worry - calls to syncdb will still work as before. A new makemigrations command provides an easy way to autodetect changes to your models and make migrations ... uments. Check the documentation for details. The allow_syncdb method on database routers is now called allow_migrate , but still performs the same function. Routers with allow_syncdb methods will still work, but that method name is deprecated and you ...
https://man.mtool.work/django/6.1/releases/1.7.html
Django 1.7 リリースノート — Django 6.1 ドキュメント 10692
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.7 リリースノート ¶ September 2, 2014 Django 1.7 へようこそ! このリリースノートでは、 バージョン 1.7 の新機能 と、Django 1.6 以前からアップグ ... Django users, as most operating-system vendors today are shipping Python 2.7 or newer as their default version. If you're still using Python 2.6, however, you'll need to stick to Django 1.6 until you can upgrade your Python version. Per our support p ... but a few of the key features are: syncdb has been deprecated and replaced by migrate . Don't worry - calls to syncdb will still work as before. A new makemigrations command provides an easy way to autodetect changes to your models and make migrations ... uments. Check the documentation for details. The allow_syncdb method on database routers is now called allow_migrate , but still performs the same function. Routers with allow_syncdb methods will still work, but that method name is deprecated and you ...
https://man.mtool.work/django/6.1/releases/1.7.html
Django 1.2 リリースノート — Django 6.1 ドキュメント 9934
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.2 リリースノート ¶ 2010 年 5 月 17 日 Django 1.2 へようこそ! Nearly a year in the making, Django 1.2 packs an impressive list of new featur ... Django users, as most operating-system vendors today are shipping Python 2.4 or newer as their default version. If you're still using Python 2.3, however, you'll need to stick to Django 1.1 until you can upgrade; per our support policy , Django 1.1 w ... onfigurable lists of validators specifying reusable, encapsulated validation behavior. Note, however, that validation must still be performed explicitly. Simply invoking a model instance's save() method will not perform any validation of the instance' ... y method available until Django 1.1. All the template loaders shipped with Django have been ported to the new API but they still implement the function-based API and the template core machinery still accepts function-based loaders (builtin or third pa ...
https://man.mtool.work/django/6.1/releases/1.2.html
Django 1.2 リリースノート — Django 6.1 ドキュメント 9934
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.2 リリースノート ¶ 2010 年 5 月 17 日 Django 1.2 へようこそ! Nearly a year in the making, Django 1.2 packs an impressive list of new featur ... Django users, as most operating-system vendors today are shipping Python 2.4 or newer as their default version. If you're still using Python 2.3, however, you'll need to stick to Django 1.1 until you can upgrade; per our support policy , Django 1.1 w ... onfigurable lists of validators specifying reusable, encapsulated validation behavior. Note, however, that validation must still be performed explicitly. Simply invoking a model instance's save() method will not perform any validation of the instance' ... y method available until Django 1.1. All the template loaders shipped with Django have been ported to the new API but they still implement the function-based API and the template core machinery still accepts function-based loaders (builtin or third pa ...
https://man.mtool.work/django/6.1/releases/1.2.html
Django 1.3.6 リリースノート — Django 6.1 ドキュメント 9549
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.3.6 リリースノート ¶ February 19, 2013 Django 1.3.6 fixes four security issues present in previous Django releases in the 1.3 series. This ... Django application. However, it has been reported to us that even with the recommended web server configurations there are still techniques available for tricking many common web servers into supplying the application with an incorrect and possibly ma ... istory 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 vi ... sues available setting history view admin previous series user domain documentation users servers ensure valid application still contain list request matching クイック検索 Last update: 2026年10月09日 « previous | up | next » ...
https://man.mtool.work/django/6.1/releases/1.3.6.html
Django 5.1.6 リリースノート — Django 6.1 ドキュメント 9549
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 5.1.6 リリースノート ¶ 2025年2月5日 Django 5.1.6 では、 5.1.5 におけるいくつかのバグを修正しました。 バグ修正 ¶ Fixed a regression in Django ... ring values ( #36098 ). Fixed a regression in Django 5.1 where password fields, despite being set to required=False , were still treated as required in forms derived from BaseUserCreationForm ( #36140 ). 目次 Django 5.1.6 リリースノート バグ修正 前のト ... グ 修正 Fixed regression validate address required リリースノート caused crash handling values password fields despite were still treated forms derived BaseUserCreationForm クイック検索 Last update: 2026年10月09日 « previous | up | next » ...
https://man.mtool.work/django/6.1/releases/5.1.6.html
Django 1.4.4 リリースノート — Django 6.1 ドキュメント 9363
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.4.4 リリースノート ¶ February 19, 2013 Django 1.4.4 fixes four security issues present in previous Django releases in the 1.4 series, as we ... Django application. However, it has been reported to us that even with the recommended web server configurations there are still techniques available for tricking many common web servers into supplying the application with an incorrect and possibly ma ... istory 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 vi ... e setting request history view admin fixes previous series improvements user domain users servers ensure valid application still list クイック検索 Last update: 2026年10月09日 « previous | up | next » ...
https://man.mtool.work/django/6.1/releases/1.4.4.html
Django 1.4 リリースノート — Django 6.1 ドキュメント 8991
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.4 リリースノート ¶ March 23, 2012 Django 1.4 へようこそ! These release notes cover the new features , as well as some backwards incompatibl ... Django users, as most operating-system vendors today are shipping Python 2.5 or newer as their default version. If you're still using Python 2.4, however, you'll need to stick to Django 1.3 until you can upgrade. Per our support policy , Django 1.3 w ... .check_password function has been moved to the django.contrib.auth.hashers module. Importing it from the old location will still work, but you should update your imports. The collectstatic management command now has a --clear option to delete all file ... e objects. It raises an exception for aware time objects. It includes milliseconds for datetime and time objects. There is still some precision loss, because Python stores microseconds (6 digits) and JSON only supports milliseconds (3 digits). However ...
https://man.mtool.work/django/6.1/releases/1.4.html
Django 1.4 リリースノート — Django 6.1 ドキュメント 8991
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.4 リリースノート ¶ March 23, 2012 Django 1.4 へようこそ! These release notes cover the new features , as well as some backwards incompatibl ... Django users, as most operating-system vendors today are shipping Python 2.5 or newer as their default version. If you're still using Python 2.4, however, you'll need to stick to Django 1.3 until you can upgrade. Per our support policy , Django 1.3 w ... .check_password function has been moved to the django.contrib.auth.hashers module. Importing it from the old location will still work, but you should update your imports. The collectstatic management command now has a --clear option to delete all file ... e objects. It raises an exception for aware time objects. It includes milliseconds for datetime and time objects. There is still some precision loss, because Python stores microseconds (6 digits) and JSON only supports milliseconds (3 digits). However ...
https://man.mtool.work/django/6.1/releases/1.4.html
Django 1.5 リリースノート — Django 6.1 ドキュメント 8419
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.5 リリースノート ¶ February 26, 2013 Django 1.5 へようこそ! These release notes cover the new features , as well as some backwards incompat ... Django users, as most operating-system vendors today are shipping Python 2.6 or newer as their default version. If you're still using Python 2.5, however, you'll need to stick to Django 1.4 until you can upgrade your Python version. Per our support p ... lates directory. Django will output some basic error messages for both situations when those templates are not found. It's still recommended as good practice to provide those templates in order to present pretty error pages to the user. django.contrib ... e reversed keyword when you're iterating on date_list in a template: {% for date in date_list reversed %} ArchiveIndexView still provides a date_list in descending order. Context in TemplateView ¶ For consistency with the design of the other generic v ...
https://man.mtool.work/django/6.1/releases/1.5.html
PREV 1 2 3 4 5 6 7 8 9 10 NEXT