summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorJason Pellerin <jpellerin@gmail.com>2006-12-04 18:04:55 +0000
committerJason Pellerin <jpellerin@gmail.com>2006-12-04 18:04:55 +0000
commit261fb45ba8ce5ad7c9a0a73c286077c779364b8d (patch)
tree6d9e7e60978a06d36bfc5e14b6ddb11359e487d9 /docs
parentf8217026f9618adb65ab2d517025e87b98ed2fbe (diff)
[multi-db] Merge trunk to [3875]. Some tests still failing.
git-svn-id: http://code.djangoproject.com/svn/django/branches/multiple-db-support@4151 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
-rw-r--r--docs/faq.txt12
-rw-r--r--docs/templates_python.txt12
2 files changed, 24 insertions, 0 deletions
diff --git a/docs/faq.txt b/docs/faq.txt
index 204c69244d..e1f344c811 100644
--- a/docs/faq.txt
+++ b/docs/faq.txt
@@ -313,6 +313,18 @@ PostgreSQL fans, and MySQL_ and `SQLite 3`_ are also supported.
.. _MySQL: http://www.mysql.com/
.. _`SQLite 3`: http://www.sqlite.org/
+Do I lose anything by using Python 2.3 versus newer Python versions, such as Python 2.5?
+----------------------------------------------------------------------------------------
+
+No. Django itself is guaranteed to work with any version of Python from 2.3
+and higher.
+
+If you use a Python version newer than 2.3, you will, of course, be able to
+take advantage of newer Python features in your own code, along with the speed
+improvements and other optimizations that have been made to the Python language
+itself. But the Django framework itself should work equally well on 2.3 as it
+does on 2.4 or 2.5.
+
Do I have to use mod_python?
----------------------------
diff --git a/docs/templates_python.txt b/docs/templates_python.txt
index bc05d769ad..39e5b9d91a 100644
--- a/docs/templates_python.txt
+++ b/docs/templates_python.txt
@@ -366,6 +366,18 @@ If ``TEMPLATE_CONTEXT_PROCESSORS`` contains this processor, every
`HttpRequest object`_. Note that this processor is not enabled by default;
you'll have to activate it.
+Writing your own context processors
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+A context processor has a very simple interface: It's just a Python function
+that takes one argument, an ``HttpRequest`` object, and returns a dictionary
+that gets added to the template context. Each context processor *must* return
+a dictionary.
+
+Custom context processors can live anywhere in your code base. All Django cares
+about is that your custom context processors are pointed-to by your
+``TEMPLATE_CONTEXT_PROCESSORS`` setting.
+
Loading templates
-----------------