Results of 1 - 10 of about 62 for can't (0.012 sec.)
- Django 1.7 リリースノート — Django 6.1 ドキュメント 9999
- 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 以前からアップグ
... y tests are collected and run. The fetch_redirect_response argument was added to assertRedirects() . Since the test client can't fetch externals URLs, this allows you to use assertRedirects with redirects that aren't part of your Django app. Correct h ... : ... except ValidationError as e : self . add_error ( None , e ) If you need both Django <= 1.6 and 1.7 compatibility you can't use Form.add_error() since it wasn't available before Django 1.7, but you can use the following workaround to convert any ...
-
https://man.mtool.work/django/6.1/releases/1.7.html
- Django 1.7 リリースノート — Django 6.1 ドキュメント 9999
- 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 以前からアップグ
... y tests are collected and run. The fetch_redirect_response argument was added to assertRedirects() . Since the test client can't fetch externals URLs, this allows you to use assertRedirects with redirects that aren't part of your Django app. Correct h ... : ... except ValidationError as e : self . add_error ( None , e ) If you need both Django <= 1.6 and 1.7 compatibility you can't use Form.add_error() since it wasn't available before Django 1.7, but you can use the following workaround to convert any ...
-
https://man.mtool.work/django/6.1/releases/1.7.html
- Django 1.5 リリースノート — Django 6.1 ドキュメント 9955
- 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
... via our automated test suite, it's received very little real-world testing. We've done our best to eliminate bugs, but we can't be sure we covered all possible uses of Django. Some features of Django aren't available because they depend on third-part ...
-
https://man.mtool.work/django/6.1/releases/1.5.html
- Django 1.5 リリースノート — Django 6.1 ドキュメント 9897
- 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
... via our automated test suite, it's received very little real-world testing. We've done our best to eliminate bugs, but we can't be sure we covered all possible uses of Django. Some features of Django aren't available because they depend on third-part ...
-
https://man.mtool.work/django/6.1/releases/1.5.html
- Django 1.6 リリースノート — Django 6.1 ドキュメント 9897
- 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
... results. Finally, there have been many changes to the ORM internal APIs. その他 ¶ The django.db.models.query.EmptyQuerySet can't be instantiated any more - it is only usable as a marker class for checking if none() has been called: isinstance(qs.none( ...
-
https://man.mtool.work/django/6.1/releases/1.6.html
- Django 1.6 リリースノート — Django 6.1 ドキュメント 9854
- 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
... results. Finally, there have been many changes to the ORM internal APIs. その他 ¶ The django.db.models.query.EmptyQuerySet can't be instantiated any more - it is only usable as a marker class for checking if none() has been called: isinstance(qs.none( ...
-
https://man.mtool.work/django/6.1/releases/1.6.html
- Django 1.4 リリースノート — Django 6.1 ドキュメント 9724
- 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
... trib.* . The expansion was performed by a filesystem-based implementation of from <package> import * . Unfortunately, this can't be done reliably. This behavior was never documented. Since it is unpythonic, it was removed in Django 1.4. If you relied ...
-
https://man.mtool.work/django/6.1/releases/1.4.html
- Django 1.4 リリースノート — Django 6.1 ドキュメント 9724
- 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
... trib.* . The expansion was performed by a filesystem-based implementation of from <package> import * . Unfortunately, this can't be done reliably. This behavior was never documented. Since it is unpythonic, it was removed in Django 1.4. If you relied ...
-
https://man.mtool.work/django/6.1/releases/1.4.html
- Submitting contributions — Django 6.1 ドキュメント 9276
- Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Submitting contributions ¶ We're always grateful for contributions to Django's code. Indeed, bug reports with associated contributions will get fixe
... e should also contain documentation. When you think your work is ready to be reviewed, send a GitHub pull request . If you can't send a pull request for some reason, you can also use patches in Trac. When using this style, follow these guidelines. Sub ...
-
https://man.mtool.work/django/6.1/internals/contributing/writing-code/submitting...
- Submitting contributions — Django 6.1 ドキュメント 9247
- Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Submitting contributions ¶ We're always grateful for contributions to Django's code. Indeed, bug reports with associated contributions will get fixe
... e should also contain documentation. When you think your work is ready to be reviewed, send a GitHub pull request . If you can't send a pull request for some reason, you can also use patches in Trac. When using this style, follow these guidelines. Sub ...
-
https://man.mtool.work/django/6.1/internals/contributing/writing-code/submitting...