per page, with , order by , clip by
Results of 1 - 10 of about 68 for working (0.002 sec.)
Working with Git and GitHub — Django 6.1 ドキュメント 13459
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Working with Git and GitHub ¶ This section explains how the community can contribute code to Django via pull requests. If you're interested in how m ... upstream You can add other remotes similarly, for example: git remote add akaariai https://github.com/akaariai/django.git Working on a ticket ¶ When working on a ticket, create a new branch for the work, and base that work on upstream/main : git checko ... . Don't hesitate to create new branches even for the smallest things - that's what they are there for. If instead you were working for a fix on the 1.4 branch, you would do: git checkout -b ticket_xxxxx_1_4 upstream/stable/1.4.x Assume the work is carri ... g: git push origin ticket_xxxxx When you go to your GitHub page, you will notice a new branch has been created. If you are working on a Trac ticket, you should mention in the ticket that your work is available from branch ticket_xxxxx of your GitHub rep ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/working-wi...
Working with Git and GitHub — Django 6.1 ドキュメント 13317
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Working with Git and GitHub ¶ This section explains how the community can contribute code to Django via pull requests. If you're interested in how m ... upstream You can add other remotes similarly, for example: git remote add akaariai https://github.com/akaariai/django.git Working on a ticket ¶ When working on a ticket, create a new branch for the work, and base that work on upstream/main : git checko ... . Don't hesitate to create new branches even for the smallest things - that's what they are there for. If instead you were working for a fix on the 1.4 branch, you would do: git checkout -b ticket_xxxxx_1_4 upstream/stable/1.4.x Assume the work is carri ... g: git push origin ticket_xxxxx When you go to your GitHub page, you will notice a new branch has been created. If you are working on a Trac ticket, you should mention in the ticket that your work is available from branch ticket_xxxxx of your GitHub rep ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/working-wi...
Django へのコントリビュート — Django 6.1 ドキュメント 10084
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django へのコントリビュート ¶ Django はボランティアで成り立っているコミュニティです。Django が成長し続けるにつれて、私たちは常に他の人を助けるために ... We're passionate about helping Django users make the jump to contributing members of the community. Communication is key - working on Django is being part of a conversation. Join it, to become familiar with what we're doing and how we talk about it. You ... process and what's involved. If you're at a contribution sprint, start here. Django フレームワークでの作業 ¶ If you enjoy working with Django, wait until you start working on it. Really, anyone can do something to improve Django, which will improve the ... ジ属性 チケットを閉じる How can I help with development? リグレッションの bisect Reviewing patches We're looking forward to working with you. Welcome aboard! 目次 Django へのコントリビュート Communication channels Join the Django community さぁ始めましょ ...
https://man.mtool.work/django/6.1/internals/contributing/
Django へのコントリビュート — Django 6.1 ドキュメント 10084
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django へのコントリビュート ¶ Django はボランティアで成り立っているコミュニティです。Django が成長し続けるにつれて、私たちは常に他の人を助けるために ... We're passionate about helping Django users make the jump to contributing members of the community. Communication is key - working on Django is being part of a conversation. Join it, to become familiar with what we're doing and how we talk about it. You ... process and what's involved. If you're at a contribution sprint, start here. Django フレームワークでの作業 ¶ If you enjoy working with Django, wait until you start working on it. Really, anyone can do something to improve Django, which will improve the ... ジ属性 チケットを閉じる How can I help with development? リグレッションの bisect Reviewing patches We're looking forward to working with you. Welcome aboard! 目次 Django へのコントリビュート Communication channels Join the Django community さぁ始めましょ ...
https://man.mtool.work/django/6.1/internals/contributing/
Django 1.6.2 リリースノート — Django 6.1 ドキュメント 10084
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.6.2 リリースノート ¶ February 6, 2014 This is Django 1.6.2, a bugfix release for Django 1.6. Django 1.6.2 fixes several bugs in 1.6.1: Prev ... ed non-ASCII characters ( #21627 ). The collectstatic command will raise an error rather than default to using the current working directory if STATIC_ROOT is not set. Combined with the --clear option, the previous behavior could wipe anything below the ... current working directory ( #21581 ). Fixed mail encoding on Python 3.3.3+ ( #21093 ). Fixed an issue where when settings.DATABASES['defau ... ノート 次のトピックへ Django 1.6.1 リリースノート 関連キーワード Fixed issue release geometry crash command default current working directory inheritance utils safe リリースノート February bugfix fixes several bugs Prevented base prepared garbage collect ...
https://man.mtool.work/django/6.1/releases/1.6.2.html
Django 1.6.2 リリースノート — Django 6.1 ドキュメント 9814
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.6.2 リリースノート ¶ February 6, 2014 This is Django 1.6.2, a bugfix release for Django 1.6. Django 1.6.2 fixes several bugs in 1.6.1: Prev ... ed non-ASCII characters ( #21627 ). The collectstatic command will raise an error rather than default to using the current working directory if STATIC_ROOT is not set. Combined with the --clear option, the previous behavior could wipe anything below the ... current working directory ( #21581 ). Fixed mail encoding on Python 3.3.3+ ( #21093 ). Fixed an issue where when settings.DATABASES['defau ... ピックへ Django 1.6.1 リリースノート 関連キーワード Django Fixed issue release geometry object crash command default current working directory inheritance django utils safe six リリースノート February bugfix 関連するページ Django 1.8.7 リリースノート Djan ...
https://man.mtool.work/django/6.1/releases/1.6.2.html
Submitting contributions — Django 6.1 ドキュメント 8055
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 ... word in the documentation, the preferred way to provide the patch is using GitHub pull requests without a Trac ticket. See Working with Git and GitHub for more details on how to use pull requests. "Claiming" tickets ¶ In an open-source project with hund ... y" section of the ticket. If it's assigned to "nobody," then it's available to be claimed. Otherwise, somebody else may be working on this ticket. Either find another bug/feature to work on, or contact the developer working on the ticket to offer your h ... GitHub pull it's claimed using work claim don't tools changes tickets feature these 関連するページ Sprint quickstart guide Working with Git and GitHub 新しいコントリビューターへのアドバイス バグレポートと機能のリクエスト チケットをトリアージする Django ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/submitting...
Sprint quickstart guide — Django 6.1 ドキュメント 7517
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Sprint quickstart guide ¶ This document explains how to prepare to contribute to Django. It is intended for use during sprints, or by people who are ... already familiar with contributing to Python open source projects. This guide assumes you're familiar with: Git (see Working with Git and GitHub ) Managing multiple versions of Python Python dependency management, including virtual environments Th ... TicketNumber tickets pip install commit work pull py cd fetch checkout push Python 関連するページ Submitting contributions Working with Git and GitHub チケットをトリアージする Djangoにはじめて貢献する Unit tests コードのコミット クイック検索 Last update ...
https://man.mtool.work/django/6.1/internals/contributing/sprint-quickstart.html
Django のセキュリティポリシー — Django 6.1 ドキュメント 7517
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django のセキュリティポリシー ¶ Django の開発チームは、セキュリティ関連の問題の責任ある報告と開示に強くコミットしています。そのため、私たちはその理想 ... Once you've submitted an issue via email, you should receive an acknowledgment from a member of the security team within 3 working days. After that, the security team will begin their analysis. Depending on the action to be taken, you may receive follow ... a triage decision, no more. It should include: A brief description of the issue and where in Django it occurs. A minimal, working proof of concept (code snippet or reproduction steps). The versions of Django and Python you tested against. Optionally, a ... ts submitted in a short period of time, and reports submitted in bulk may be put on hold. Reporting guidelines ¶ Include a working proof of concept ¶ Please privately share a minimal Django project or code snippet that demonstrates the potential vulnera ...
https://man.mtool.work/django/6.1/internals/security.html
Pythonモジュール索引 — Django 6.1 ドキュメント 7517
Django 6.1 ドキュメント Home | Table of contents | Index | Modules up Pythonモジュール索引 a | c | d | f | h | m | s | t | u | v a django.apps c django.conf django.conf.urls django.conf.urls.i18n django.contrib django.contrib.admin Django's ... ng, cookie handling, ...) django.utils.log Logging tools for Django applications django.utils.module_loading Functions for working with Python modules. django.utils.safestring Functions and classes for working with strings that can be displayed safely w ...
https://man.mtool.work/django/6.1/py-modindex.html
PREV 1 2 3 4 5 6 7 NEXT