README

@@ -1,37 +1,48 @@
-Django is a high-level Python Web framework that encourages rapid development
+Django is a high-level Python Web framework that encourages rapid
-and clean, pragmatic design.
+development and clean, pragmatic design.
 
-All documentation is in the "docs" directory and online at
-http://www.djangoproject.com/documentation/.  If you're just getting started,
-here's how we recommend you read the docs:
 
-    * First, read docs/install.txt for instructions on installing Django.
+About this version
+==================
 
-    * Next, work through the tutorials in order (docs/tutorial01.txt,
+This is the Django 0.90 "bugfixes" branch, which is intended to
-      docs/tutorial02.txt, etc.).
+provide bugfix and patch support for users of Django 0.90 who have not
+been able to migrate to a more recent version. No new features will be
+added in this branch, and it is maintained solely as a means of
+providing support to legacy Django installations.
 
-    * If you want to set up an actual deployment server, read docs/modpython.txt
+If you're completely new to Django we highly recommend that you use
-      for instructions on running Django under mod_python.
+either the latest stable release or a Subversion checkout from
+Django's trunk; Django is always evolving, and the latest and greatest
+features are only available to users of newer versions of the
+framework.
 
-    * The rest of the documentation is of the reference-manual variety.
-      Read it -- and the FAQ -- as you run into problems.
 
-Docs are updated rigorously. If you find any problems in the docs, or think they
+More information
-should be clarified in any way, please take 30 seconds to fill out a ticket
+================
-here:
 
-http://code.djangoproject.com/newticket
+The complete history of bugs fixed in this branch can be viewed online
+at http://code.djangoproject.com/log/django/branches/0.90-bugfixes.
 
-To get more help:
+We also recommend that users of this branch subscribe to the
+"django-announce" mailing list, a low-traffic, announcements-only list
+which will send messages whenever an important (i.e.,
+security-related) bug is fixed. You can subscribe to the list via
+Google Groups at http://groups.google.com/group/django-announce.
 
-    * Join the #django channel on irc.freenode.net. Lots of helpful people
+The documentation for this version of Django has been frozen, and is
-      hang out there. Read the archives at http://loglibrary.com/179 .
+available online at http://www.djangoproject.com/documentation/0_90/.
 
-    * Join the django-users mailing list, or read the archives, at
-      http://groups-beta.google.com/group/django-users.
 
-To contribute to Django:
+Submitting bugs
+===============
 
-    * Check out http://www.djangoproject.com/community/ for information
+If you run into a bug in Django 0.90, please search the Django ticket
-      about getting involved.
+database to see if the issue has already been reported; if not, please
+head over to http://code.djangoproject.com/newticket and file a new
+ticket with as much information about the bug as you can provide.
 
+If you're running into a bug which has been reported but not fixed,
+feel free to update the ticket with any additional information you
+have, and to assign it to 'ubernostrum' (AKA James Bennett, the
+maintainer of this branch).

django/bin/compile-messages.py

@@ -19,6 +19,13 @@ for (dirpath, dirnames, filenames) in os.walk(basedir):
         if file.endswith('.po'):
             sys.stderr.write('processing file %s in %s\n' % (file, dirpath))
             pf = os.path.splitext(os.path.join(dirpath, file))[0]
-            cmd = 'msgfmt -o %s.mo %s.po' % (pf, pf)
+            # Store the names of the .mo and .po files in an environment
+            # variable, rather than doing a string replacement into the
+            # command, so that we can take advantage of shell quoting, to
+            # quote any malicious characters/escaping.
+            # See http://cyberelk.net/tim/articles/cmdline/ar01s02.html
+            os.environ['djangocompilemo'] = pf + '.mo'
+            os.environ['djangocompilepo'] = pf + '.po'
+            cmd = 'msgfmt -o "$djangocompilemo" "$djangocompilepo"'
             os.system(cmd)
 

django/core/db/backends/postgresql.py

@@ -9,13 +9,45 @@ import psycopg as Database
 
 DatabaseError = Database.DatabaseError
 
+def smart_basestring(s, charset):
+    if isinstance(s, unicode):
+        return s.encode(charset)
+    return s
+
+class UnicodeCursorWrapper(object):
+    """
+    A thin wrapper around psycopg cursors that allows them to accept Unicode
+    strings as params.
+
+    This is necessary because psycopg doesn't apply any DB quoting to
+    parameters that are Unicode strings. If a param is Unicode, this will
+    convert it to a bytestring using DEFAULT_CHARSET before passing it to
+    psycopg.
+    """
+    def __init__(self, cursor, charset):
+        self.cursor = cursor
+        self.charset = charset
+
+    def execute(self, sql, params=()):
+        return self.cursor.execute(sql, [smart_basestring(p, self.charset) for p in params])
+
+    def executemany(self, sql, param_list):
+        new_param_list = [tuple([smart_basestring(p, self.charset) for p in params]) for params in param_list]
+        return self.cursor.executemany(sql, new_param_list)
+
+    def __getattr__(self, attr):
+        if self.__dict__.has_key(attr):
+            return self.__dict__[attr]
+        else:
+            return getattr(self.cursor, attr)
+
 class DatabaseWrapper:
     def __init__(self):
         self.connection = None
         self.queries = []
 
     def cursor(self):
-        from django.conf.settings import DATABASE_USER, DATABASE_NAME, DATABASE_HOST, DATABASE_PORT, DATABASE_PASSWORD, DEBUG, TIME_ZONE
+        from django.conf.settings import DATABASE_USER, DATABASE_NAME, DATABASE_HOST, DATABASE_PORT, DATABASE_PASSWORD, DEBUG, DEFAULT_CHARSET, TIME_ZONE
         if self.connection is None:
             if DATABASE_NAME == '':
                 from django.core.exceptions import ImproperlyConfigured
@@ -33,6 +65,7 @@ class DatabaseWrapper:
             self.connection.set_isolation_level(1) # make transactions transparent to all cursors
         cursor = self.connection.cursor()
         cursor.execute("SET TIME ZONE %s", [TIME_ZONE])
+        cursor = UnicodeCursorWrapper(cursor, DEFAULT_CHARSET)
         if DEBUG:
             return base.CursorDebugWrapper(cursor, self)
         return cursor

django/core/handlers/modpython.py

@@ -137,13 +137,12 @@ class ModPythonHandler(BaseHandler):
         try:
             request = ModPythonRequest(req)
             response = self.get_response(req.uri, request)
+            # Apply response middleware
+            for middleware_method in self._response_middleware:
+                response = middleware_method(request, response)
         finally:
             db.db.close()
 
-        # Apply response middleware
-        for middleware_method in self._response_middleware:
-            response = middleware_method(request, response)
-
         # Convert our custom HttpResponse object back into the mod_python req.
         populate_apache_request(response, req)
         return 0 # mod_python.apache.OK

django/core/meta/__init__.py

@@ -1126,9 +1126,9 @@ def _get_where_clause(lookup_type, table_prefix, field_name, value):
         pass
     if lookup_type == 'in':
         return '%s%s IN (%s)' % (table_prefix, field_name, ','.join(['%s' for v in value]))
-    elif lookup_type in ('range', 'year'):
+    elif lookup_type == 'range':
         return '%s%s BETWEEN %%s AND %%s' % (table_prefix, field_name)
-    elif lookup_type in ('month', 'day'):
+    elif lookup_type in ('year', 'month', 'day'):
         return "%s = %%s" % db.get_date_extract_sql(lookup_type, table_prefix + field_name)
     elif lookup_type == 'isnull':
         return "%s%s IS %sNULL" % (table_prefix, field_name, (not value and 'NOT ' or ''))

django/core/meta/fields.py

@@ -157,12 +157,10 @@ class Field(object):
 
     def get_db_prep_lookup(self, lookup_type, value):
         "Returns field's value prepared for database lookup."
-        if lookup_type in ('exact', 'gt', 'gte', 'lt', 'lte', 'ne', 'month', 'day'):
+        if lookup_type in ('exact', 'gt', 'gte', 'lt', 'lte', 'ne', 'year', 'month', 'day'):
             return [value]
         elif lookup_type in ('range', 'in'):
             return value
-        elif lookup_type == 'year':
-            return ['%s-01-01' % value, '%s-12-31' % value]
         elif lookup_type in ('contains', 'icontains'):
             return ["%%%s%%" % prep_for_like_query(value)]
         elif lookup_type == 'iexact':