per page, with , order by , clip by
Results of 1 - 10 of about 82 for tuple (0.005 sec.)
Django 1.11.17 リリースノート — Django 6.1 ドキュメント 10475
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.11.17 リリースノート ¶ December 3, 2018 Django 1.11.17 では、1.11.16 にあったいくつかのバグを修正し、Python 3.7 との互換性を追加しました。 ... バグ修正 ¶ Prevented repetitive calls to geos_version_tuple() in the WKBWriter class in an attempt to fix a random crash involving LooseVersion since Django 1.11.14 ( #29959 ). 目次 ... ックへ Django 1.11.16 リリースノート 関連キーワード バグ 修正 リリースノート December 互換性 Prevented repetitive calls geos tuple WKBWriter attempt random crash involving LooseVersion since クイック検索 Last update: 2026年10月09日 « previous | up | nex ...
https://man.mtool.work/django/6.1/releases/1.11.17.html
How to release Django — Django 6.1 ドキュメント 9876
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up How to release Django ¶ このドキュメントでは、Django のリリース方法について説明しています。 これらの手順を変更した場合は、最新の情報を保ってください! ここでの ... it to be merged after the stable branch is cut. The following items should be addressed in this branch: Update the VERSION tuple in django/__init__.py , incrementing to the next expected release ( example commit ). Create a stub release note for the n ... ecurity commit ). Update the version number in django/__init__.py for the release. Please see notes on setting the VERSION tuple below for details on VERSION ( example commit ). If this is a pre-release package also update the "Development Status" tro ... og post. Post-release ¶ You're almost done! All that's left to do now is: If this is not a pre-release, update the VERSION tuple in django/__init__.py again, incrementing to whatever the next expected release will be. For example, after releasing 4.1. ...
https://man.mtool.work/django/6.1/internals/howto-release-django.html
Django 1.11.17 リリースノート — Django 6.1 ドキュメント 9876
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.11.17 リリースノート ¶ December 3, 2018 Django 1.11.17 では、1.11.16 にあったいくつかのバグを修正し、Python 3.7 との互換性を追加しました。 ... バグ修正 ¶ Prevented repetitive calls to geos_version_tuple() in the WKBWriter class in an attempt to fix a random crash involving LooseVersion since Django 1.11.14 ( #29959 ). 目次 ... リリースノート 関連キーワード Django バグ 修正 リリースノート December いくつ Python 互換性 Prevented repetitive calls geos tuple WKBWriter class attempt fix random crash involving 関連するページ Django 2.1.4 リリースノート Django 4.2.8 リリースノート ...
https://man.mtool.work/django/6.1/releases/1.11.17.html
Django 6.1 release notes — Django 6.1 ドキュメント 9876
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 6.1 release notes ¶ August 5, 2026 Welcome to Django 6.1! These release notes cover the new features , as well as some backwards incompatible ... defining the natural_key() method can now opt out of natural key serialization by overriding the method to return an empty tuple: () . This ensures primary keys are serialized when using dumpdata --natural-primary . The XML deserializer now raises Sus ... de this method to simply return the value. The DatabaseIntrospection.get_relations() should now return a dictionary with 3-tuples containing ( field_name_other_table , other_table , db_on_delete ) as values. db_on_delete is one of the database-level d ... ary_placeholder_sql() method now expects a query compiler as an extra positional argument and should return a two-elements tuple composed of an SQL format string and a tuple of associated parameters. The BaseSpatialOperations.get_geom_placeholder() me ...
https://man.mtool.work/django/6.1/releases/6.1.html
How to release Django — Django 6.1 ドキュメント 9876
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up How to release Django ¶ このドキュメントでは、Django のリリース方法について説明しています。 これらの手順を変更した場合は、最新の情報を保ってください! ここでの ... it to be merged after the stable branch is cut. The following items should be addressed in this branch: Update the VERSION tuple in django/__init__.py , incrementing to the next expected release ( example commit ). Create a stub release note for the n ... ecurity commit ). Update the version number in django/__init__.py for the release. Please see notes on setting the VERSION tuple below for details on VERSION ( example commit ). If this is a pre-release package also update the "Development Status" tro ... og post. Post-release ¶ You're almost done! All that's left to do now is: If this is not a pre-release, update the VERSION tuple in django/__init__.py again, incrementing to whatever the next expected release will be. For example, after releasing 4.1. ...
https://man.mtool.work/django/6.1/internals/howto-release-django.html
Django 2.1.4 リリースノート — Django 6.1 ドキュメント 9876
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 2.1.4 リリースノート ¶ December 3, 2018 Django 2.1.4 では、2.1.3 にあったいくつかのバグを修正しました。 バグ修正 ¶ Corrected the default pass ... rcasing all passwords to match the format expected by the validator ( #29952 ). Prevented repetitive calls to geos_version_tuple() in the WKBWriter class in an attempt to fix a random crash involving LooseVersion ( #29959 ). Fixed keep-alive support i ... rd list CommonPasswordValidator uses lowercasing passwords match format expected validator Prevented repetitive calls geos tuple クイック検索 Last update: 2026年10月09日 « previous | up | next » ...
https://man.mtool.work/django/6.1/releases/2.1.4.html
Django 6.1 release notes — Django 6.1 ドキュメント 9876
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 6.1 release notes ¶ August 5, 2026 Welcome to Django 6.1! These release notes cover the new features , as well as some backwards incompatible ... defining the natural_key() method can now opt out of natural key serialization by overriding the method to return an empty tuple: () . This ensures primary keys are serialized when using dumpdata --natural-primary . The XML deserializer now raises Sus ... de this method to simply return the value. The DatabaseIntrospection.get_relations() should now return a dictionary with 3-tuples containing ( field_name_other_table , other_table , db_on_delete ) as values. db_on_delete is one of the database-level d ... ary_placeholder_sql() method now expects a query compiler as an extra positional argument and should return a two-elements tuple composed of an SQL format string and a tuple of associated parameters. The BaseSpatialOperations.get_geom_placeholder() me ...
https://man.mtool.work/django/6.1/releases/6.1.html
Django 6.0 release notes — Django 6.1 ドキュメント 9672
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 6.0 release notes ¶ December 3, 2025 Welcome to Django 6.0! These release notes cover the new features , as well as some backwards incompatib ... o_field = 'django.db.models.AutoField' to an app's AppConfig , as needed. Custom ORM expressions should return params as a tuple ¶ Prior to Django 6.0, custom lookups and custom expressions implementing the as_sql() method (and its supporting methods ... process_lhs() and process_rhs() ) were allowed to return a sequence of params in either a list or a tuple. To address the interoperability problems that resulted, the second return element of the as_sql() method should now be a ... tuple: def as_sql ( self , compiler , connection ) -> tuple [ str , tuple ]: ... If your custom expressions support multiple versions of Django, you should adjust any pre-processing ...
https://man.mtool.work/django/6.1/releases/6.0.html
Django 6.0 release notes — Django 6.1 ドキュメント 9672
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 6.0 release notes ¶ December 3, 2025 Welcome to Django 6.0! These release notes cover the new features , as well as some backwards incompatib ... o_field = 'django.db.models.AutoField' to an app's AppConfig , as needed. Custom ORM expressions should return params as a tuple ¶ Prior to Django 6.0, custom lookups and custom expressions implementing the as_sql() method (and its supporting methods ... process_lhs() and process_rhs() ) were allowed to return a sequence of params in either a list or a tuple. To address the interoperability problems that resulted, the second return element of the as_sql() method should now be a ... tuple: def as_sql ( self , compiler , connection ) -> tuple [ str , tuple ]: ... If your custom expressions support multiple versions of Django, you should adjust any pre-processing ...
https://man.mtool.work/django/6.1/releases/6.0.html
Django の admin サイト — Django 6.1 ドキュメント 8486
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django の admin サイト ¶ Django のパワフルな特徴の1つは、自動的に生成される admin インタフェースです。あなたのモデルクラスからメタデータを読み取り、 ... と同じルールが適用されます: 呼び出し可能オブジェクトは readonly_fields 内でリスト化される必要があります。 classes A list or tuple containing extra CSS classes to apply to the fieldset. This can include any custom CSS class defined in the project, as we ... elated() メソッドを実装できます。 バージョン 6.1 で非推奨: Using True for list_select_related is deprecated. Use a list or tuple of field names instead. 注釈 ModelAdmin は select_related() がチェンジリストの QuerySet で既に呼び出されていた場合、この属 ... readonly_fields ¶ デフォルトでは、すべてのフィールドが編集可能となっています。このオプションに含まれるフィールド ( list か tuple で指定します) は、データをそのまま表示するだけで編集できなくなります。また、追加と編集に使われる ModelForm からも除外されま ...
https://man.mtool.work/django/6.1/ref/contrib/admin/
PREV 1 2 3 4 5 6 7 8 9 NEXT