per page, with , order by , clip by
Results of 1 - 10 of about 226 for like (0.007 sec.)
Django 1.7 リリースノート — Django 6.1 ドキュメント 9182
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 以前からアップグ ... "entries" ) . all () New system check framework ¶ We've added a new System check framework for detecting common problems (like invalid models) and providing hints for resolving those problems. The framework is extensible so you can add your own chec ... the QuerySet used to traverse a given relation or customize the storage location of prefetch results. This enables things like filtering prefetched relations, calling select_related() from a prefetched relation, or prefetching the same relation mult ... close () Custom lookups ¶ It is now possible to write custom lookups and transforms for the ORM. Custom lookups work just like Django's built-in lookups (e.g. lte , icontains ) while transforms are a new concept. The django.db.models.Lookup class pr ...
https://man.mtool.work/django/6.1/releases/1.7.html
Django 1.7 リリースノート — Django 6.1 ドキュメント 9182
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 以前からアップグ ... "entries" ) . all () New system check framework ¶ We've added a new System check framework for detecting common problems (like invalid models) and providing hints for resolving those problems. The framework is extensible so you can add your own chec ... the QuerySet used to traverse a given relation or customize the storage location of prefetch results. This enables things like filtering prefetched relations, calling select_related() from a prefetched relation, or prefetching the same relation mult ... close () Custom lookups ¶ It is now possible to write custom lookups and transforms for the ORM. Custom lookups work just like Django's built-in lookups (e.g. lte , icontains ) while transforms are a new concept. The django.db.models.Lookup class pr ...
https://man.mtool.work/django/6.1/releases/1.7.html
Django 1.4 リリースノート — Django 6.1 ドキュメント 8840
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 ... on . 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 testing frameworks (like Sele ... lpful FAQ . Support for in-browser testing frameworks ¶ Django 1.4 supports integration with in-browser testing frameworks like Selenium . The new django.test.LiveServerTestCase base class lets you test the interactions between your site's front and ... work as before until Django 1.6. In 1.5 it will raise DeprecationWarning ). The new recommended manage.py file should look like this: #!/usr/bin/env python import os , sys if __name__ == "__main__" : os . environ . setdefault ( "DJANGO_SETTINGS_MODUL ...
https://man.mtool.work/django/6.1/releases/1.4.html
Django 1.4 リリースノート — Django 6.1 ドキュメント 8840
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 ... on . 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 testing frameworks (like Sele ... lpful FAQ . Support for in-browser testing frameworks ¶ Django 1.4 supports integration with in-browser testing frameworks like Selenium . The new django.test.LiveServerTestCase base class lets you test the interactions between your site's front and ... work as before until Django 1.6. In 1.5 it will raise DeprecationWarning ). The new recommended manage.py file should look like this: #!/usr/bin/env python import os , sys if __name__ == "__main__" : os . environ . setdefault ( "DJANGO_SETTINGS_MODUL ...
https://man.mtool.work/django/6.1/releases/1.4.html
Django 1.6 リリースノート — Django 6.1 ドキュメント 8157
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.6 リリースノート ¶ 注釈 Dedicated to Malcolm Tredinnick On March 17, 2013, the Django project and the free software community lost a very d ... r deprecation plan , and we've begun the deprecation process for some features . Python バージョン間の互換性 ¶ Django 1.6, like Django 1.5, requires Python 2.6.5 or above. Python 3 is also officially supported. We highly recommend the latest minor re ... greSQL. The blocktrans template tag now respects TEMPLATE_STRING_IF_INVALID for variables not present in the context, just like other template constructs. SimpleLazyObject s will now present more helpful representations in shell debugging situations. ... nges in transaction management may result in additional statements to create, release or rollback savepoints. This is more likely to happen with SQLite, since it didn't support savepoints until this release. If tests using assertNumQueries() fail bec ...
https://man.mtool.work/django/6.1/releases/1.6.html
Django 1.6 リリースノート — Django 6.1 ドキュメント 8157
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.6 リリースノート ¶ 注釈 Dedicated to Malcolm Tredinnick On March 17, 2013, the Django project and the free software community lost a very d ... r deprecation plan , and we've begun the deprecation process for some features . Python バージョン間の互換性 ¶ Django 1.6, like Django 1.5, requires Python 2.6.5 or above. Python 3 is also officially supported. We highly recommend the latest minor re ... greSQL. The blocktrans template tag now respects TEMPLATE_STRING_IF_INVALID for variables not present in the context, just like other template constructs. SimpleLazyObject s will now present more helpful representations in shell debugging situations. ... nges in transaction management may result in additional statements to create, release or rollback savepoints. This is more likely to happen with SQLite, since it didn't support savepoints until this release. If tests using assertNumQueries() fail bec ...
https://man.mtool.work/django/6.1/releases/1.6.html
Contributing code — Django 6.1 ドキュメント 7981
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Contributing code ¶ So you'd like to write some code, documentation or tests to improve Django? There are several ways you can help Django's develop ... butions 関連キーワード Django code How to tests write documentation contains topics run work we easy pickings Contributing like improve There several ways help クイック検索 Last update: 2026年10月08日 « previous | up | next » ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/
Django 1.5.1 リリースノート — Django 6.1 ドキュメント 7981
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.5.1 リリースノート ¶ March 28, 2013 This is Django 1.5.1, a bugfix release for Django 1.5. It's completely backwards compatible with Django ... . Under certain circumstances, repeated iteration over querysets could leak memory - sometimes quite a bit of it. If you'd like more information, the details are in our ticket tracker (and in a related issue in Python itself). If you've noticed memor ... ly backwards compatible handful biggest introduced certain circumstances repeated iteration over querysets sometimes quite like more クイック検索 Last update: 2026年10月09日 « previous | up | next » ...
https://man.mtool.work/django/6.1/releases/1.5.1.html
Contributing code — Django 6.1 ドキュメント 7805
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Contributing code ¶ So you'd like to write some code, documentation or tests to improve Django? There are several ways you can help Django's develop ... mitting contributions 関連キーワード code How to tests write documentation contains topics work easy pickings Contributing like improve There several ways help development Tutorials tutorial whole section walks step-by-step through クイック検索 Last ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/
Migrating email to mailers — Django 6.1 ドキュメント 7464
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Migrating email to mailers ¶ Django 6.1 introduced the MAILERS setting, replacing EMAIL_BACKEND and several other EMAIL_* settings. It also introduc ... n . send_messages ([ email1 , email2 ]) Note that mailers.default is the default for Django's mail-sending functions. Code like this: mail . send_mail ( ... , connection = mail . get_connection ()) can be updated to: mail . send_mail ( ... ) # No con ... "BACKEND" : "path.to.custom.EmailBackend" , "OPTIONS" : { "option1" : True , "option2" : "value" , }, }, } And then use it like this: mail . send_mail ( ... , using = "custom" ) mail . mailers [ "custom" ] . send_messages ([ email1 , email2 ]) Replac ... try / except OSError: pass . Note that this ignores both transient network glitches and SMTP configuration problems (just like the existing SMTP email backend fail_silently implementation). To ignore end user typos in to addresses and other delivery ...
https://man.mtool.work/django/6.1/howto/mailers-migration.html
PREV 1 2 3 4 5 6 7 8 9 10 NEXT