per page, with , order by , clip by
Results of 1 - 10 of about 52 for warnings (0.005 sec.)
Submitting contributions — Django 6.1 ドキュメント 13113
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 ... sion where the feature will be removed) when the deprecated feature is invoked. Assuming we have good test coverage, these warnings are converted to errors when running the test suite with warnings enabled: python -Wa runtests.py . Thus, when adding a Re ... movedInDjangoXXXXWarning you need to eliminate or silence any warnings generated when running the tests. The first step is to remove any use of the deprecated behavior by Django itself. Next yo ... u can silence warnings in tests that actually test the deprecated behavior by using the ignore_warnings decorator, either at the test or class le ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/submitting...
Submitting contributions — Django 6.1 ドキュメント 12948
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 ... sion where the feature will be removed) when the deprecated feature is invoked. Assuming we have good test coverage, these warnings are converted to errors when running the test suite with warnings enabled: python -Wa runtests.py . Thus, when adding a Re ... movedInDjangoXXXXWarning you need to eliminate or silence any warnings generated when running the tests. The first step is to remove any use of the deprecated behavior by Django itself. Next yo ... u can silence warnings in tests that actually test the deprecated behavior by using the ignore_warnings decorator, either at the test or class le ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/submitting...
Django 2.2.14 リリースノート — Django 6.1 ドキュメント 10365
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 2.2.14 リリースノート ¶ July 1, 2020 Django 2.2.14 fixes a bug in 2.2.13. バグ修正 ¶ Fixed messages of InvalidCacheKey exceptions and CacheKe ... yWarning warnings raised by cache key validation ( #31654 ). 目次 Django 2.2.14 リリースノート バグ修正 前のトピックへ Django 2.2.15 リリース ... リリースノート 関連キーワード リリースノート July fixes バグ 修正 Fixed messages InvalidCacheKey exceptions CacheKeyWarning warnings raised cache validation クイック検索 Last update: 2026年10月09日 « previous | up | next » ...
https://man.mtool.work/django/6.1/releases/2.2.14.html
Django 2.2.14 リリースノート — Django 6.1 ドキュメント 9887
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 2.2.14 リリースノート ¶ July 1, 2020 Django 2.2.14 fixes a bug in 2.2.13. バグ修正 ¶ Fixed messages of InvalidCacheKey exceptions and CacheKe ... yWarning warnings raised by cache key validation ( #31654 ). 目次 Django 2.2.14 リリースノート バグ修正 前のトピックへ Django 2.2.15 リリース ... ート 関連キーワード Django リリースノート July fixes bug バグ 修正 Fixed messages InvalidCacheKey exceptions CacheKeyWarning warnings raised cache key validation 関連するページ Django 3.0.8 リリースノート Django 3.0.7 リリースノート Django 1.11.26 リリース ...
https://man.mtool.work/django/6.1/releases/2.2.14.html
Django 3.0.8 リリースノート — Django 6.1 ドキュメント 9558
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 3.0.8 リリースノート ¶ July 1, 2020 Django 3.0.8 では、3.0.7 におけるいくつかのバグを修正しました。 バグ修正 ¶ Fixed messages of InvalidCache ... Key exceptions and CacheKeyWarning warnings raised by cache key validation ( #31654 ). Fixed a regression in Django 3.0.7 that caused a queryset crash when grouping b ... ド Fixed regression バグ 修正 caused queryset crash リリースノート July messages InvalidCacheKey exceptions CacheKeyWarning warnings raised cache validation grouping many relationship Reallowed following expressions filterable attribute クイック検索 Last ...
https://man.mtool.work/django/6.1/releases/3.0.8.html
Django 3.0.8 リリースノート — Django 6.1 ドキュメント 9394
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 3.0.8 リリースノート ¶ July 1, 2020 Django 3.0.8 では、3.0.7 におけるいくつかのバグを修正しました。 バグ修正 ¶ Fixed messages of InvalidCache ... Key exceptions and CacheKeyWarning warnings raised by cache key validation ( #31654 ). Fixed a regression in Django 3.0.7 that caused a queryset crash when grouping b ... ression バグ 修正 key caused queryset crash リリースノート July いくつ messages InvalidCacheKey exceptions CacheKeyWarning warnings raised cache validation 関連するページ Django 2.2.14 リリースノート Django 3.0.7 リリースノート Django 2.0.4 リリースノート ...
https://man.mtool.work/django/6.1/releases/3.0.8.html
Migrating email to mailers — Django 6.1 ドキュメント 9245
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 ... verify their compatibility with MAILERS before making other changes. Update email-related settings . Run with deprecation warnings enabled (see 廃止予定警告を解決する ) to identify other code needing updates. 注釈 Running tests may not identify all rele ... a non-functional email backend (such as the memory backend that Django substitutes during tests ), so can miss deprecation warnings that are only issued from the production email configuration. Consider running with deprecation warnings enabled in produc ... ings have been upgraded to use MAILERS . (If they use any deprecated mail features, those will of course cause deprecation warnings.) There are two deprecated features that are not supported when MAILERS is defined in a project's settings: Trying to acce ...
https://man.mtool.work/django/6.1/howto/mailers-migration.html
Migrating email to mailers — Django 6.1 ドキュメント 9245
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 ... verify their compatibility with MAILERS before making other changes. Update email-related settings . Run with deprecation warnings enabled (see 廃止予定警告を解決する ) to identify other code needing updates. 注釈 Running tests may not identify all rele ... a non-functional email backend (such as the memory backend that Django substitutes during tests ), so can miss deprecation warnings that are only issued from the production email configuration. Consider running with deprecation warnings enabled in produc ... ings have been upgraded to use MAILERS . (If they use any deprecated mail features, those will of course cause deprecation warnings.) There are two deprecated features that are not supported when MAILERS is defined in a project's settings: Trying to acce ...
https://man.mtool.work/django/6.1/howto/mailers-migration.html
Django の機能廃止のタイムライン — Django 6.1 ドキュメント 7945
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django の機能廃止のタイムライン ¶ このドキュメントは、 非推奨化ポリシー に従って、Django の様々なパーツが互換性を伴わない方法で変更または削除されるタ ... cleanup.py script will be removed. The depth keyword argument will be removed from select_related() . The undocumented get_warnings_state() / restore_warnings_state() functions from django.test.utils and the save_warnings_state() / restore_warnings_state ... () django.test.*TestCase methods are deprecated. Use the warnings.catch_warnings context manager available starting with Python 2.6 instead. The undocumented check_for_test_cookie method i ...
https://man.mtool.work/django/6.1/internals/deprecation.html
Django の機能廃止のタイムライン — Django 6.1 ドキュメント 7945
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django の機能廃止のタイムライン ¶ このドキュメントは、 非推奨化ポリシー に従って、Django の様々なパーツが互換性を伴わない方法で変更または削除されるタ ... cleanup.py script will be removed. The depth keyword argument will be removed from select_related() . The undocumented get_warnings_state() / restore_warnings_state() functions from django.test.utils and the save_warnings_state() / restore_warnings_state ... () django.test.*TestCase methods are deprecated. Use the warnings.catch_warnings context manager available starting with Python 2.6 instead. The undocumented check_for_test_cookie method i ...
https://man.mtool.work/django/6.1/internals/deprecation.html
PREV 1 2 3 4 5 6 NEXT