When deploying a Django application into a real production environment, you\nwill almost always want to use an official packaged release of Django.
\nHowever, if you’d like to try out in-development code from an upcoming release\nor contribute to the development of Django, you’ll need to obtain a clone of\nDjango’s source code repository.
\nThis document covers the way the code repository is laid out and how to work\nwith and find things in it.
\nThe Django source code repository uses Git to track changes to the code\nover time, so you’ll need a copy of the Git client (a program called git)\non your computer, and you’ll want to familiarize yourself with the basics of\nhow Git works.
Git’s website offers downloads for various operating systems. The site also\ncontains vast amounts of documentation.
\nThe Django Git repository is located online at github.com/django/django. It contains the full source code for all\nDjango releases, which you can browse online.
\nThe Git repository includes several branches:
\nmaster contains the main in-development code which will become\nthe next packaged release of Django. This is where most development\nactivity is focused.
stable/A.B.x are the branches where release preparation work happens.\nThey are also used for bugfix and security releases which occur as necessary\nafter the initial release of a feature version.
soc20XX/<project> branches were used by students who worked on Django\nduring the 2009 and 2010 Google Summer of Code programs.
attic/<project> branches were used to develop major or experimental new\nfeatures without affecting the rest of Django’s code.
The Git repository also contains tags. These are the exact revisions from\nwhich packaged Django releases were produced, since version 1.0.
\nThe source code for the Djangoproject.com\nwebsite can be found at github.com/django/djangoproject.com.
\nIf you’d like to try out the in-development code for the next release of\nDjango, or if you’d like to contribute to Django by fixing bugs or developing\nnew features, you’ll want to get the code from the master branch.
\nNote that this will get all of Django: in addition to the top-level\ndjango module containing Python code, you’ll also get a copy of Django’s\ndocumentation, test suite, packaging scripts and other miscellaneous bits.\nDjango’s code will be present in your clone as a directory named\ndjango.
To try out the in-development code with your own applications, simply place\nthe directory containing your clone on your Python import path. Then\nimport statements which look for Django will find the django module\nwithin your clone.
If you’re going to be working on Django’s code (say, to fix a bug or\ndevelop a new feature), you can probably stop reading here and move\nover to the documentation for contributing to Django, which covers things like the preferred\ncoding style and how to generate and submit a patch.
\nDjango uses branches to prepare for releases of Django.
\nIn the past when Django was hosted on Subversion, branches were also used for\nfeature development. Now Django is hosted on Git and feature development is\ndone on contributor’s forks, but the Subversion feature branches remain in Git\nfor historical reference.
\nThese branches can be found in the repository as stable/A.B.x\nbranches and will be created right after the first alpha is tagged.
For example, immediately after Django 1.5 alpha 1 was tagged, the branch\nstable/1.5.x was created and all further work on preparing the code for the\nfinal 1.5 release was done there.
These branches also provide bugfix and security support as described in\nVersions prises en charge.
\nFor example, after the release of Django 1.5, the branch stable/1.5.x\nreceives only fixes for security and critical stability bugs, which are\neventually released as Django 1.5.1 and so on, stable/1.4.x receives only\nsecurity and data loss fixes, and stable/1.3.x no longer receives any\nupdates.
Feature-development branches tend by their nature to be temporary. Some\nproduce successful features which are merged back into Django’s master to\nbecome part of an official release, but others do not; in either case, there\ncomes a time when the branch is no longer being actively worked on by any\ndeveloper. At this point the branch is considered closed.
\nUnfortunately, Django used to be maintained with the Subversion revision\ncontrol system, that has no standard way of indicating this. As a workaround,\nbranches of Django which are closed and no longer maintained were moved into\nattic.
For reference, the following are branches whose code eventually became\npart of Django itself, and so are no longer separately maintained:
\nboulder-oracle-sprint: Added support for Oracle databases to\nDjango’s object-relational mapper. This has been part of Django\nsince the 1.0 release.
gis: Added support for geographic/spatial queries to Django’s\nobject-relational mapper. This has been part of Django since the 1.0\nrelease, as the bundled application django.contrib.gis.
i18n: Added internationalization support to\nDjango. This has been part of Django since the 0.90 release.
magic-removal: A major refactoring of both the internals and\npublic APIs of Django’s object-relational mapper. This has been part\nof Django since the 0.95 release.
multi-auth: A refactoring of Django’s bundled\nauthentication framework which added support for\nauthentication backends. This has\nbeen part of Django since the 0.95 release.
new-admin: A refactoring of Django’s bundled\nadministrative application. This became part of\nDjango as of the 0.91 release, but was superseded by another\nrefactoring (see next listing) prior to the Django 1.0 release.
newforms-admin: The second refactoring of Django’s bundled\nadministrative application. This became part of Django as of the 1.0\nrelease, and is the basis of the current incarnation of\ndjango.contrib.admin.
queryset-refactor: A refactoring of the internals of Django’s\nobject-relational mapper. This became part of Django as of the 1.0\nrelease.
unicode: A refactoring of Django’s internals to consistently use\nUnicode-based strings in most places within Django and Django\napplications. This became part of Django as of the 1.0 release.
When Django moved from Subversion to Git, the information about branch merges\nwasn’t preserved in the source code repository. This means that the master\nbranch of Django doesn’t contain merge commits for the above branches.
However, this information is available as a grafts file. You can restore it\nby putting the following lines in .git/info/grafts in your local clone:
ac64e91a0cadc57f4bc5cd5d66955832320ca7a1 553a20075e6991e7a60baee51ea68c8adc520d9a 0cb8e31823b2e9f05c4ae868c19f5f38e78a5f2e\n79e68c225b926302ebb29c808dda8afa49856f5c d0f57e7c7385a112cb9e19d314352fc5ed5b0747 aa239e3e5405933af6a29dac3cf587b59a099927\n5cf8f684237ab5addaf3549b2347c3adf107c0a7 cb45fd0ae20597306cd1f877efc99d9bd7cbee98 e27211a0deae2f1d402537f0ebb64ad4ccf6a4da\nf69cf70ed813a8cd7e1f963a14ae39103e8d5265 d5dbeaa9be359a4c794885c2e9f1b5a7e5e51fb8 d2fcbcf9d76d5bb8a661ee73dae976c74183098b\naab3a418ac9293bb4abd7670f65d930cb0426d58 4ea7a11659b8a0ab07b0d2e847975f7324664f10 adf4b9311d5d64a2bdd58da50271c121ea22e397\nff60c5f9de3e8690d1e86f3e9e3f7248a15397c8 7ef212af149540aa2da577a960d0d87029fd1514 45b4288bb66a3cda401b45901e85b645674c3988\n9dda4abee1225db7a7b195b84c915fdd141a7260 4fe5c9b7ee09dc25921918a6dbb7605edb374bc9 3a7c14b583621272d4ef53061287b619ce3c290d\na19ed8aea395e8e07164ff7d85bd7dff2f24edca dc375fb0f3b7fbae740e8cfcd791b8bccb8a4e66 42ea7a5ce8aece67d16c6610a49560c1493d4653\n9c52d56f6f8a9cdafb231adf9f4110473099c9b5 c91a30f00fd182faf8ca5c03cd7dbcf8b735b458 4a5c5c78f2ecd4ed8859cd5ac773ff3a01bccf96\n953badbea5a04159adbfa970f5805c0232b6a401 4c958b15b250866b70ded7d82aa532f1e57f96ae 5664a678b29ab04cad425c15b2792f4519f43928\n471596fc1afcb9c6258d317c619eaf5fd394e797 4e89105d64bb9e04c409139a41e9c7aac263df4c 3e9035a9625c8a8a5e88361133e87ce455c4fc13\n9233d0426537615e06b78d28010d17d5a66adf44 6632739e94c6c38b4c5a86cf5c80c48ae50ac49f 18e151bc3f8a85f2766d64262902a9fcad44d937\nAdditionally, the following branches are closed, but their code was\nnever merged into Django and the features they aimed to implement\nwere never finished:
\nfull-history
generic-auth
multiple-db-support
per-object-permissions
schema-evolution
schema-evolution-ng
search-api
sqlalchemy
All of the above-mentioned branches now reside in attic.
Finally, the repository contains soc2009/xxx and soc2010/xxx feature\nbranches, used for the 2009 and 2010 Google Summer of Code projects.
Each Django release is tagged and signed by the releaser.
\nThe tags can be found on GitHub’s tags page.
\n