per page, with , order by , clip by
Results of 1 - 10 of about 72 for follow (0.006 sec.)
Submitting contributions — Django 6.1 ドキュメント 12122
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 ... apable of fixing it (as measured by your coding ability, knowledge of Django internals and time availability), claim it by following these steps: Log in using your GitHub account or create an account in our ticket system. If you have an account but hav ... icket for this issue doesn't exist yet, create one in our ticket tracker . Remember that proposals for new features should follow the process for suggesting new features . If a ticket for this issue already exists and has been accepted, make sure nobod ... if you happen to have the changes ready. Contribution style ¶ Make sure that any contribution you do fulfills at least the following requirements: The code required to fix a problem or add a feature is an essential part of a solution, but it is not the ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/submitting...
Submitting contributions — Django 6.1 ドキュメント 12122
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 ... apable of fixing it (as measured by your coding ability, knowledge of Django internals and time availability), claim it by following these steps: Log in using your GitHub account or create an account in our ticket system. If you have an account but hav ... icket for this issue doesn't exist yet, create one in our ticket tracker . Remember that proposals for new features should follow the process for suggesting new features . If a ticket for this issue already exists and has been accepted, make sure nobod ... if you happen to have the changes ready. Contribution style ¶ Make sure that any contribution you do fulfills at least the following requirements: The code required to fix a problem or add a feature is an essential part of a solution, but it is not the ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/submitting...
テストツール — Django 6.1 ドキュメント 11520
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » テストツール ¶ Django は、テストを書くのに便利なツールをいくつか提供しています。 There are community-maintained solutions! Django has a vibrant ecos ... ーダを指定できます。 Client インスタンスを一度作れば、以下のメソッドを自由に使うことができます。 get ( path , data = None , follow = False , secure = False , * , headers = None , query_params = None , ** extra ) [ソース] ¶ 与えられた path に対して GET リ ... =7" ) エンコード済みのGETデータを含むURLと query_params または data 引数の両方を指定した場合、これらの引数が優先されます。 follow を True を与えると、クライアントはすべてのリダイレクトを辿り、途中の URL とステータスコードのタプルが、レスポンスオブジェク ... l/ にリダイレクトするような場合には、 redirect_chain は次のような値になります。 >>> response = c . get ( "/redirect_me/" , follow = True ) >>> response . redirect_chain [('http://testserver/next/', 302), ('http://testserver/final/', 302)] secure を Tru ...
https://man.mtool.work/django/6.1/topics/testing/tools.html
テストツール — Django 6.1 ドキュメント 11127
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » テストツール ¶ Django は、テストを書くのに便利なツールをいくつか提供しています。 There are community-maintained solutions! Django has a vibrant ecos ... ーダを指定できます。 Client インスタンスを一度作れば、以下のメソッドを自由に使うことができます。 get ( path , data = None , follow = False , secure = False , * , headers = None , query_params = None , ** extra ) [ソース] ¶ 与えられた path に対して GET リ ... =7" ) エンコード済みのGETデータを含むURLと query_params または data 引数の両方を指定した場合、これらの引数が優先されます。 follow を True を与えると、クライアントはすべてのリダイレクトを辿り、途中の URL とステータスコードのタプルが、レスポンスオブジェク ... l/ にリダイレクトするような場合には、 redirect_chain は次のような値になります。 >>> response = c . get ( "/redirect_me/" , follow = True ) >>> response . redirect_chain [('http://testserver/next/', 302), ('http://testserver/final/', 302)] secure を Tru ...
https://man.mtool.work/django/6.1/topics/testing/tools.html
Coding style — Django 6.1 ドキュメント 9515
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Coding style ¶ Please follow these coding standards when writing code for inclusion in Django. Pre-commit checks ¶ pre-commit is a framework for man ... tespace issues. The Python files use 4 spaces for indentation and the HTML files use 2 spaces. Unless otherwise specified, follow PEP 8 . Use flake8 to check for problems in this area. Note that our .flake8 file excludes some errors that we don't consi ... t poll.getUniqueVoters() ). Use InitialCaps for class names (or for factory functions that return classes). In docstrings, follow the style of existing docstrings and PEP 257 . In tests, use assertRaisesMessage() and assertWarnsMessage() instead of ass ... t View 代わりに、次のようにします::代わりに、次のようにします: from django.views.generic.base import View Template style ¶ Follow the below rules in Django template code. {% extends %} should be the first non-comment line. Do this: {% extends "base.htm ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/coding-sty...
Coding style — Django 6.1 ドキュメント 9319
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Coding style ¶ Please follow these coding standards when writing code for inclusion in Django. Pre-commit checks ¶ pre-commit is a framework for man ... tespace issues. The Python files use 4 spaces for indentation and the HTML files use 2 spaces. Unless otherwise specified, follow PEP 8 . Use flake8 to check for problems in this area. Note that our .flake8 file excludes some errors that we don't consi ... t poll.getUniqueVoters() ). Use InitialCaps for class names (or for factory functions that return classes). In docstrings, follow the style of existing docstrings and PEP 257 . In tests, use assertRaisesMessage() and assertWarnsMessage() instead of ass ... t View 代わりに、次のようにします::代わりに、次のようにします: from django.views.generic.base import View Template style ¶ Follow the below rules in Django template code. {% extends %} should be the first non-comment line. Do this: {% extends "base.htm ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/coding-sty...
バグレポートと機能のリクエスト — Django 6.1 ドキュメント 8520
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » バグレポートと機能のリクエスト ¶ 重要 Please report security issues only to security@djangoproject.com . This is a private list only open to long-ti ... . Reporting user interface bugs ¶ If your bug impacts anything visual in nature, there are a few additional guidelines to follow: 最小のテストケースが視覚的に理解できるスクリーンショットをチケットに含めてください。あなたの素晴らしいブラウザのカスタマイ ... consensus. Emoji reactions are used on issues within the new feature ideas GitHub project to track community feedback. The following meanings are assigned to each reaction: ?: I support this feature and would use it ?: I oppose this feature or believe ... ition The Steering Council will regularly review the ideas in the project, moving those with community support through the following stages: アイデア Approved - Idea refinement - Team creation 進行中 Working solution - Review - Feedback Needs maintaine ...
https://man.mtool.work/django/6.1/internals/contributing/bugs-and-features.html
バグレポートと機能のリクエスト — Django 6.1 ドキュメント 8520
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » バグレポートと機能のリクエスト ¶ 重要 Please report security issues only to security@djangoproject.com . This is a private list only open to long-ti ... . Reporting user interface bugs ¶ If your bug impacts anything visual in nature, there are a few additional guidelines to follow: 最小のテストケースが視覚的に理解できるスクリーンショットをチケットに含めてください。あなたの素晴らしいブラウザのカスタマイ ... consensus. Emoji reactions are used on issues within the new feature ideas GitHub project to track community feedback. The following meanings are assigned to each reaction: ?: I support this feature and would use it ?: I oppose this feature or believe ... ition The Steering Council will regularly review the ideas in the project, moving those with community support through the following stages: アイデア Approved - Idea refinement - Team creation 進行中 Working solution - Review - Feedback Needs maintaine ...
https://man.mtool.work/django/6.1/internals/contributing/bugs-and-features.html
Django のセキュリティポリシー — Django 6.1 ドキュメント 8114
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django のセキュリティポリシー ¶ Django の開発チームは、セキュリティ関連の問題の責任ある報告と開示に強くコミットしています。そのため、私たちはその理想 ... orking days. After that, the security team will begin their analysis. Depending on the action to be taken, you may receive followup emails. It can take several weeks before the security team comes to a conclusion. There is no need to chase the security ... nsive upfront analysis makes triage slower, not faster. If the team confirms the issue is a valid vulnerability, they will follow up and welcome further detail at that stage. If you have identified multiple potential issues, please wait for a triage re ... responsibility to properly handle user input. This principle is explained in our security documentation . For example, the following is not considered valid because email has not been sanitized: from django.core.mail import send_mail from django.http i ...
https://man.mtool.work/django/6.1/internals/security.html
Django のセキュリティポリシー — Django 6.1 ドキュメント 8114
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django のセキュリティポリシー ¶ Django の開発チームは、セキュリティ関連の問題の責任ある報告と開示に強くコミットしています。そのため、私たちはその理想 ... orking days. After that, the security team will begin their analysis. Depending on the action to be taken, you may receive followup emails. It can take several weeks before the security team comes to a conclusion. There is no need to chase the security ... nsive upfront analysis makes triage slower, not faster. If the team confirms the issue is a valid vulnerability, they will follow up and welcome further detail at that stage. If you have identified multiple potential issues, please wait for a triage re ... responsibility to properly handle user input. This principle is explained in our security documentation . For example, the following is not considered valid because email has not been sanitized: from django.core.mail import send_mail from django.http i ...
https://man.mtool.work/django/6.1/internals/security.html
PREV 1 2 3 4 5 6 7 8 NEXT