Go to file
Claude Paroz 1b6e751430 [1.5.x] Fixed #19226 -- Applied linebreaksbr to read-only fields in admin
Thanks shadow for the report, and Melevir and thiderman for the
patch.
Backport of ec9d6b112 from master.
2012-11-17 17:12:24 +01:00
.tx Updated Transifex base url 2012-10-15 14:19:41 +02:00
django [1.5.x] Fixed #19226 -- Applied linebreaksbr to read-only fields in admin 2012-11-17 17:12:24 +01:00
docs [1.5.x] Fixed #19310 -- changed method docs formatting for custom file storage docs 2012-11-17 07:13:37 -08:00
extras Made more extensive usage of context managers with open. 2012-05-05 14:06:36 +02:00
scripts Fixed #11184 -- Made it possible to build RPMs with a non-default python executable. 2012-01-02 20:09:58 +00:00
tests [1.5.x] Fixed #19226 -- Applied linebreaksbr to read-only fields in admin 2012-11-17 17:12:24 +01:00
.gitignore Fixed #16817 - Added a guide of code coverage to contributing docs. 2012-10-11 06:11:52 -04:00
.hgignore Fixed #16817 - Added a guide of code coverage to contributing docs. 2012-10-11 06:11:52 -04:00
AUTHORS [1.5.X] Fixed #16671 - Added a tutorial on reuseable apps 2012-10-30 18:41:29 -04:00
CONTRIBUTING.rst Fixed #18971 -- added root level CONTRIBUTING doc 2012-09-17 22:09:07 -07:00
INSTALL Updated installation instructions. 2012-05-15 10:08:34 +02:00
LICENSE Updated LICENSE file to acknowledge individual copyrights as well (after 2008-08-09 14:40:51 +00:00
MANIFEST.in Ensure we ignore __pycache__ PEP 3174 dirs in a few more places. 2012-10-06 18:40:58 -03:00
README.rst Fix bullet formatting for README.rst. 2012-04-28 21:20:39 +01:00
setup.cfg Fixed #18874 -- Updated new name of README.rst to auxiliary files 2012-08-29 21:25:02 +02:00
setup.py [1.5.x] We actually only support 3.2+ on Py3k. 2012-10-25 14:21:02 -05:00

README.rst

Django is a high-level Python Web framework that encourages rapid development
and clean, pragmatic design. Thanks for checking it out.

All documentation is in the "docs" directory and online at
http://docs.djangoproject.com/en/dev/. If you're just getting started, here's
how we recommend you read the docs:

* First, read docs/intro/install.txt for instructions on installing Django.

* Next, work through the tutorials in order (docs/intro/tutorial01.txt,
  docs/intro/tutorial02.txt, etc.).

* If you want to set up an actual deployment server, read
  docs/howto/deployment/index.txt for instructions.

* You'll probably want to read through the topical guides (in docs/topics)
  next; from there you can jump to the HOWTOs (in docs/howto) for specific
  problems, and check out the reference (docs/ref) for gory details.

* See docs/README for instructions on building an HTML version of the docs.

Docs are updated rigorously. If you find any problems in the docs, or think they
should be clarified in any way, please take 30 seconds to fill out a ticket
here:

http://code.djangoproject.com/newticket

To get more help:

* Join the #django channel on irc.freenode.net. Lots of helpful people hang out
  there. Read the archives at http://django-irc-logs.com/.

* Join the django-users mailing list, or read the archives, at
  http://groups.google.com/group/django-users.

To contribute to Django:

* Check out http://www.djangoproject.com/community/ for information about
  getting involved.

To run Django's test suite:

* Follow the instructions in the "Unit tests" section of
  docs/internals/contributing/writing-code/unit-tests.txt, published online at
  https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/unit-tests/#running-the-unit-tests