... Django's documentation, test suite, packaging scripts and other miscellaneous bits. Django's code will be present in your clone as a directory named django . To try out the in-development code with your own applications, place the directory containin ... g your clone on your Python import path. Then import statements which look for Django will find the django module within your clone. If ... tHub's tags page. Archived feature-development work ¶ Historical information Since Django moved to Git in 2012, anyone can clone the repository and create their own branches, alleviating the need for official branches in the source code repository. Th ... ... Django's documentation, test suite, packaging scripts and other miscellaneous bits. Django's code will be present in your clone as a directory named django . To try out the in-development code with your own applications, place the directory containin ... g your clone on your Python import path. Then import statements which look for Django will find the django module within your clone. If ... tHub's tags page. Archived feature-development work ¶ Historical information Since Django moved to Git in 2012, anyone can clone the repository and create their own branches, alleviating the need for official branches in the source code repository. Th ... ... are unfamiliar, see Djangoにはじめて貢献する for a longer, step-by-step tutorial. Set up ¶ Fork the repository on GitHub, clone your fork to your machine, and configure a remote reference to Django's upstream repository: / $ git clone https://git ... hub.com/YourGitHubName/django.git $ cd django $ git remote add upstream https://github.com/django/django.git ...\> git clone https://github.com/YourGitHubName/django.git ...\> cd django ...\> git remote add upstream https://github.com/django/djang ... ... are unfamiliar, see Djangoにはじめて貢献する for a longer, step-by-step tutorial. Set up ¶ Fork the repository on GitHub, clone your fork to your machine, and configure a remote reference to Django's upstream repository: / $ git clone https://git ... hub.com/YourGitHubName/django.git $ cd django $ git remote add upstream https://github.com/django/django.git ...\> git clone https://github.com/YourGitHubName/django.git ...\> cd django ...\> git remote add upstream https://github.com/django/djang ... ... カルコピーのディレクトリに移動しましょう。 以下のコマンドで Django のソースコードリポジトリをダウンロードします: / $ git clone https://github.com/YourGitHubName/django.git ...\> git clone https://github.com/YourGitHubName/django.git 低帯域の回線をご ... 利用ですか? You can add the --depth 1 argument to git clone to skip downloading all of Django's commit history, which reduces data transfer from ~250 MB to ~70 MB. Django のローカルコ ... 先に進んで、以前にクローンしたDjangoのコピーをインストールしてください: / $ python -m pip install -e /path/to/your/local/clone/django/ ...\> py -m pip install -e \path\to\your\local\clone\django\ インストールされる Django のバージョンは、編集可能モー ... ... d your GitHub account, with the nick "GitHub_nick", and forked Django's repository , create a local copy of your fork: git clone https://github.com/GitHub_nick/django.git This will create a new directory "django", containing a clone of your GitHub rep ... ository. The rest of the git commands on this page need to be run within the cloned directory, so switch to it now: cd django Your GitHub repository will be called "origin" in Git. You should also set up d ... ry of this branch, by using git rebase for example. Other people shouldn't base their work on such a branch, because their clone would become corrupt when you edit commits. There are also "public branches". These are branches other people are supposed ... ... d your GitHub account, with the nick "GitHub_nick", and forked Django's repository , create a local copy of your fork: git clone https://github.com/GitHub_nick/django.git This will create a new directory "django", containing a clone of your GitHub rep ... ository. The rest of the git commands on this page need to be run within the cloned directory, so switch to it now: cd django Your GitHub repository will be called "origin" in Git. You should also set up d ... ry of this branch, by using git rebase for example. Other people shouldn't base their work on such a branch, because their clone would become corrupt when you edit commits. There are also "public branches". These are branches other people are supposed ... ... カルコピーのディレクトリに移動しましょう。 以下のコマンドで Django のソースコードリポジトリをダウンロードします: / $ git clone https://github.com/YourGitHubName/django.git ...\> git clone https://github.com/YourGitHubName/django.git 低帯域の回線をご ... 利用ですか? You can add the --depth 1 argument to git clone to skip downloading all of Django's commit history, which reduces data transfer from ~250 MB to ~70 MB. Django のローカルコ ... 先に進んで、以前にクローンしたDjangoのコピーをインストールしてください: / $ python -m pip install -e /path/to/your/local/clone/django/ ...\> py -m pip install -e \path\to\your\local\clone\django\ インストールされる Django のバージョンは、編集可能モー ... ... e_expressions ( expressions ) ¶ 式のリストを受け取り、それを get_source_expressions() が返せるように格納します。 relabeled_clone ( change_map ) ¶ self のクローン（コピー）を返し、すべてのカラムエイリアスが再ラベル付けされます。カラムエイリアスは、サブ ... クエリが作成される際に名前が変更されます。 relabeled_clone() は、任意のネストされた式にも呼び出され、クローンに割り当てられるべきです。 change_map は古いエイリアスを新しいエイリアス ... にマッピングする辞書です。 実装例: def relabeled_clone ( self , change_map ): clone = copy . copy ( self ) clone . expression = self . expression . relabeled_clone ( change_map ... ... e_expressions ( expressions ) ¶ 式のリストを受け取り、それを get_source_expressions() が返せるように格納します。 relabeled_clone ( change_map ) ¶ self のクローン（コピー）を返し、すべてのカラムエイリアスが再ラベル付けされます。カラムエイリアスは、サブ ... クエリが作成される際に名前が変更されます。 relabeled_clone() は、任意のネストされた式にも呼び出され、クローンに割り当てられるべきです。 change_map は古いエイリアスを新しいエイリアス ... にマッピングする辞書です。 実装例: def relabeled_clone ( self , change_map ): clone = copy . copy ( self ) clone . expression = self . expression . relabeled_clone ( change_map ... 2026年10月08日