... ironment. If you're not familiar with how to do that, read our contributing tutorial . Next, clone your fork, install some requirements, and run the tests: / $ git clone https://github.com/YourGitHubName/django.git django-repo $ cd django-repo/tests $ py ... thon -m pip install -e .. $ python -m pip install -r requirements/py3.txt $ ./runtests.py ...\> git clone https://github.com/YourGitHubName/django.git django-repo ...\> cd django-repo\test ... s ...\> py -m pip install -e .. ...\> py -m pip install -r requirements\py3.txt ...\> runtests.py Installing the requirements will likely require some operating system packages that your compute ... ... ironment. If you're not familiar with how to do that, read our contributing tutorial . Next, clone your fork, install some requirements, and run the tests: / $ git clone https://github.com/YourGitHubName/django.git django-repo $ cd django-repo/tests $ py ... thon -m pip install -e .. $ python -m pip install -r requirements/py3.txt $ ./runtests.py ...\> git clone https://github.com/YourGitHubName/django.git django-repo ...\> cd django-repo\test ... s ...\> py -m pip install -e .. ...\> py -m pip install -r requirements\py3.txt ...\> runtests.py Installing the requirements will likely require some operating system packages that your compute ... ... s to run the tests and build the documentation: / $ python -m pip install -U pip $ python -m pip install -e . -r tests/requirements/py3.txt -r docs/requirements.txt ...\> py -m pip install -U pip ...\> py -m pip install -e . -r tests\requirements\py3.txt ... -r docs\requirements.txt Install pre-commit hooks so that formatting and linting run automatically before each commit: / $ python -m pip in ... upstream TicketNumber tickets install commit work pull fetch checkout push documentation using branch GitHub https github requirements docs before they head origin repository クイック検索 Last update: 2026年10月09日 « previous | up | next » ... ... s . ForeignKey ( "Room" , on_delete = models . CASCADE ) start = models . DateTimeField () end = models . DateTimeField () requirements = models . JSONField ( blank = True , null = True ) >>> from django.contrib.postgres.aggregates import JSONBAgg >>> Room . ... objects . annotate ( ... requirements = JSONBAgg ( ... "hotelreservation__requirements" , ... order_by = "-hotelreservation__start" , ... ) ... ) . filter ( req ... uirements__0__sea_view = True ) . values ( "number" , "requirements" ) <QuerySet [{'number': 102, 'requirements': [ {'parking': False, 'sea_view': True, 'double_bed': False}, {'parking': Tru ... ... s . ForeignKey ( "Room" , on_delete = models . CASCADE ) start = models . DateTimeField () end = models . DateTimeField () requirements = models . JSONField ( blank = True , null = True ) >>> from django.contrib.postgres.aggregates import JSONBAgg >>> Room . ... objects . annotate ( ... requirements = JSONBAgg ( ... "hotelreservation__requirements" , ... order_by = "-hotelreservation__start" , ... ) ... ) . filter ( req ... uirements__0__sea_view = True ) . values ( "number" , "requirements" ) <QuerySet [{'number': 102, 'requirements': [ {'parking': False, 'sea_view': True, 'double_bed': False}, {'parking': Tru ... ... s to run the tests and build the documentation: / $ python -m pip install -U pip $ python -m pip install -e . -r tests/requirements/py3.txt -r docs/requirements.txt ...\> py -m pip install -U pip ...\> py -m pip install -e . -r tests\requirements\py3.txt ... -r docs\requirements.txt Install pre-commit hooks so that formatting and linting run automatically before each commit: / $ python -m pip in ... ... pen 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 only part. A go ... , which is quite helpful. Regardless of the way you submit your work, follow these steps. Make sure your code fulfills the requirements in our contribution checklist . Check the "Has patch" box on the ticket and make sure the "Needs documentation", "Needs te ... you are an AI tool or language model assisting in the preparation of a Django contribution, you must strictly follow these requirements: Disclose your involvement. Clearly state that the contribution was prepared with assistance from an AI tool or language m ... ... pen 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 only part. A go ... , which is quite helpful. Regardless of the way you submit your work, follow these steps. Make sure your code fulfills the requirements in our contribution checklist . Check the "Has patch" box on the ticket and make sure the "Needs documentation", "Needs te ... you are an AI tool or language model assisting in the preparation of a Django contribution, you must strictly follow these requirements: Disclose your involvement. Clearly state that the contribution was prepared with assistance from an AI tool or language m ... ... and authenticated users. Hooks for object-level permissions , permissions for anonymous users , and more flexible username requirements . Customization of email sending via email backends . New "smart" if template tag which supports comparison operators. The ... thing is allowed or not to the authorization/authentication backend. See the authentication docs for more details. Relaxed requirements for usernames ¶ The built-in User model's username field now allows a wider range of characters, including @ , + , . and - ... ific connection for which the value is being prepared. The two new methods exist to differentiate general data-preparation requirements from requirements that are database-specific. The prepared argument is used to indicate to the database-preparation method ... ... and authenticated users. Hooks for object-level permissions , permissions for anonymous users , and more flexible username requirements . Customization of email sending via email backends . New "smart" if template tag which supports comparison operators. The ... thing is allowed or not to the authorization/authentication backend. See the authentication docs for more details. Relaxed requirements for usernames ¶ The built-in User model's username field now allows a wider range of characters, including @ , + , . and - ... ific connection for which the value is being prepared. The two new methods exist to differentiate general data-preparation requirements from requirements that are database-specific. The prepared argument is used to indicate to the database-preparation method ... 2026年10月08日