Re: [Django] #8997: Misleading error message when calling get_absolute_url

[Django]

#8997: Misleading error message when calling get_absolute_url
-+--
  Reporter:  Rob   | Owner:  
nobody
Status:  new | Milestone:   
 
 Component:  Database layer (models, ORM)|   Version:  1.2  
 
Resolution:  |  Keywords:   
 
 Stage:  Design decision needed  | Has_patch:  0
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  0   |  
-+--
Changes (by joshlory):

  * version:  1.1 => 1.2

Comment:

 The test case proposed by GDorn appears to be fixed: creating a model with
 a get_absolute_url() function containing a divide by zero correctly
 returns a 500 Debug page when DEBUG=True.  However the original bug
 (misleading error with a typo in a field name) is still present in Django
 1.2.3.  How to make this happen:

 Create a model with a get_absolute_url function that references an invalid
 field, e.g.:

 {{{
 def get_absolute_url(self):
 return "/foo/bar/" + self.invalid_field
 }}}

 Hook the model up to the django admin. Create one of these models. Click
 the 'view on site' button.

 '''Expected behavior:''' When DEBUG=True, display a 500 Debug page showing
 an {{{AttributeError}}} in the model.

 '''Actual output:''' Django reports a 404 error: " objects don't have
 get_absolute_url() methods".

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14018: Introduce class_plural %-substitution placeholder for related_name of ForeignKey/ManyToManyField

[Django]

#14018: Introduce class_plural %-substitution placeholder for related_name of
ForeignKey/ManyToManyField
---+
  Reporter:  puxlit| Owner:  nobody 
   
Status:  new   | Milestone:  2.0
   
 Component:  Database layer (models, ORM)  |   Version:  SVN
   
Resolution:|  Keywords:  
related_name, ManyToManyField, ForeignKey, abstract base class
 Stage:  Design decision needed| Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  1 |  
---+
Changes (by puxlit):

  * milestone:  1.3 => 2.0

Comment:

 Replying to [comment:1 anonymous] and [comment:2 mk]:
 Good point; I hadn't considered `verbose_name_plural`s with multiple
 and/or internationalised words.

 Replying to [comment:3 lrekucki]:
 That's a rather elegant solution. I agree that it's more of a nice touch
 than a must-have feature, but I make use of this patch in my code, and
 don't believe there's any harm in including it.

 Thanks for all the suggestions! I'm presently working on a patch with
 updated documentation and a set of test cases.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #14746: Update request/response docs

[Django]

#14746: Update request/response docs
---+
 Reporter:  adamv  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 Update the http request/response docs:

   * Link more settings
   * Link more classes
   * Pull out UploadedFile class to separate section
   * Fix outline level of QueryDict class

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #14745: Update shortcuts docs

[Django]

#14745: Update shortcuts docs
---+
 Reporter:  adamv  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 Update shortcuts docs to link up more classes, tweak a weird
 'versionadded" placement, and quote some inline code.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #14744: Update views docs

[Django]

#14744: Update views docs
---+
 Reporter:  adamv  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 Updated the views docs with more class & settings cross-links

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #14743: Clean up "urls" documentation

[Django]

#14743: Clean up "urls" documentation
---+
 Reporter:  adamv  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 Clean up URLs documentation, including:
   * Link settings
   * Fix some function/method/class links
   * Fix quotes in a code example

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #14742: Allow each action to decide default value for select_across

[Django]

#14742: Allow each action to decide default value for select_across
--+-
 Reporter:  cur...@tinbrain.net   |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  1.3-alpha 
 Keywords:  admin, actions|   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 It seems the "select_across" option in Admin actions is under-utilised
 [e.g. not at all].

 It would allow an action to not require any selected items, instead
 operating on all matching the current filter spec.

 However, because of a duplicate check it never gets the chance.

 The attached patch removes the check, changes select_across to
 NullBooleanField, with Null as default, and will set it to the
 select_across property of the selected action if it has one, or False
 otherwise.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Changeset] r14655 - in django/trunk: django/db/models docs/ref/models tests/modeltests/lookup

[noreply]

Author: carljm
Date: 2010-11-20 20:28:25 -0600 (Sat, 20 Nov 2010)
New Revision: 14655

Modified:
   django/trunk/django/db/models/query.py
   django/trunk/docs/ref/models/querysets.txt
   django/trunk/tests/modeltests/lookup/models.py
   django/trunk/tests/modeltests/lookup/tests.py
Log:
Fixed #5768 -- Added support for ManyToManyFields and reverse relations in 
values() and values_list(). Thanks to mrmachine for the patch.

Modified: django/trunk/django/db/models/query.py
===
--- django/trunk/django/db/models/query.py  2010-11-20 23:57:01 UTC (rev 
14654)
+++ django/trunk/django/db/models/query.py  2010-11-21 02:28:25 UTC (rev 
14655)
@@ -870,7 +870,7 @@
 self.query.select = []
 if self.extra_names is not None:
 self.query.set_extra_mask(self.extra_names)
-self.query.add_fields(self.field_names, False)
+self.query.add_fields(self.field_names, True)
 if self.aggregate_names is not None:
 self.query.set_aggregate_mask(self.aggregate_names)
 

Modified: django/trunk/docs/ref/models/querysets.txt
===
--- django/trunk/docs/ref/models/querysets.txt  2010-11-20 23:57:01 UTC (rev 
14654)
+++ django/trunk/docs/ref/models/querysets.txt  2010-11-21 02:28:25 UTC (rev 
14655)
@@ -398,11 +398,8 @@
 >>> Blog.objects.values('id', 'name')
 [{'id': 1, 'name': 'Beatles Blog'}]
 
-A couple of subtleties that are worth mentioning:
+A few subtleties that are worth mentioning:
 
-* The ``values()`` method does not return anything for
-  :class:`~django.db.models.ManyToManyField` attributes and will raise an
-  error if you try to pass in this type of field to it.
 * If you have a field called ``foo`` that is a
   :class:`~django.db.models.ForeignKey`, the default ``values()`` call
   will return a dictionary key called ``foo_id``, since this is the name
@@ -453,6 +450,28 @@
 but it doesn't really matter. This is your chance to really flaunt your
 individualism.
 
+.. versionchanged:: 1.3
+
+The ``values()`` method previously did not return anything for
+:class:`~django.db.models.ManyToManyField` attributes and would raise an error
+if you tried to pass this type of field to it.
+
+This restriction has been lifted, and you can now also refer to fields on
+related models with reverse relations through ``OneToOneField``, ``ForeignKey``
+and ``ManyToManyField`` attributes::
+
+   Blog.objects.values('name', 'entry__headline')
+   [{'name': 'My blog', 'entry__headline': 'An entry'},
+ {'name': 'My blog', 'entry__headline': 'Another entry'}, ...]
+
+.. warning::
+
+   Because :class:`~django.db.models.ManyToManyField` attributes and reverse
+   relations can have multiple related rows, including these can have a
+   multiplier effect on the size of your result set. This will be especially
+   pronounced if you include multiple such fields in your ``values()`` query,
+   in which case all possible combinations will be returned.
+
 ``values_list(*fields)``
 
 

Modified: django/trunk/tests/modeltests/lookup/models.py
===
--- django/trunk/tests/modeltests/lookup/models.py  2010-11-20 23:57:01 UTC 
(rev 14654)
+++ django/trunk/tests/modeltests/lookup/models.py  2010-11-21 02:28:25 UTC 
(rev 14655)
@@ -7,11 +7,23 @@
 from django.db import models, DEFAULT_DB_ALIAS, connection
 from django.conf import settings
 
+class Author(models.Model):
+name = models.CharField(max_length=100)
+class Meta:
+ordering = ('name', )
+
 class Article(models.Model):
 headline = models.CharField(max_length=100)
 pub_date = models.DateTimeField()
+author = models.ForeignKey(Author, blank=True, null=True)
 class Meta:
 ordering = ('-pub_date', 'headline')
 
 def __unicode__(self):
 return self.headline
+
+class Tag(models.Model):
+articles = models.ManyToManyField(Article)
+name = models.CharField(max_length=100)
+class Meta:
+ordering = ('name', )

Modified: django/trunk/tests/modeltests/lookup/tests.py
===
--- django/trunk/tests/modeltests/lookup/tests.py   2010-11-20 23:57:01 UTC 
(rev 14654)
+++ django/trunk/tests/modeltests/lookup/tests.py   2010-11-21 02:28:25 UTC 
(rev 14655)
@@ -3,28 +3,43 @@
 from django.core.exceptions import FieldError
 from django.db import connection
 from django.test import TestCase, skipUnlessDBFeature
-from models import Article
+from models import Author, Article, Tag
 
 
 class LookupTests(TestCase):
 
 #def setUp(self):
 def setUp(self):
+# Create a few Authors.
+self.au1 = Author(name='Author 1')
+self.au1.save()
+self.au2 = Author(name='Author 2')
+self.au2.save()
 # Create a couple of 

Re: [Django] #14655: formsets should be iterable

[Django]

#14655: formsets should be iterable
---+
  Reporter:  kenth | Owner:  pandres
Status:  reopened  | Milestone: 
 Component:  Forms |   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by kenth):

  * needs_tests:  1 => 0

Comment:

 Added tests. As a result, I added __getitem__ & __len__ methods to the
 patch. Several of the tests indexed `formset.forms`.

 Passes tests. Ready for review.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #5768: Allow QuerySet.values() to return values spanning joins (for multi-valued relations)

[Django]

#5768: Allow QuerySet.values() to return values spanning joins (for multi-valued
relations)
-+--
  Reporter:  anonymous   | Owner:   
 
Status:  new | Milestone:   
 
 Component:  Database layer (models, ORM)|   Version:  SVN  
 
Resolution:  |  Keywords:  
values, values_list, one-to-many, many-to-many reverse
 Stage:  Ready for checkin   | Has_patch:  1
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  0   |  
-+--
Comment (by mrmachine):

 Full test suite for sqlite and postgresql just passed, too. I didn't do
 mysql after I found out it was going to take 10+ hours or have a bunch of
 other failures.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #5768: Allow QuerySet.values() to return values spanning joins (for multi-valued relations)

[Django]

#5768: Allow QuerySet.values() to return values spanning joins (for multi-valued
relations)
-+--
  Reporter:  anonymous   | Owner:   
 
Status:  new | Milestone:   
 
 Component:  Database layer (models, ORM)|   Version:  SVN  
 
Resolution:  |  Keywords:  
values, values_list, one-to-many, many-to-many reverse
 Stage:  Ready for checkin   | Has_patch:  1
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  0   |  
-+--
Changes (by mrmachine):

  * needs_better_patch:  1 => 0
  * stage:  Accepted => Ready for checkin

Comment:

 Apologies, I should have ran the tests for postgresql and mysql as well.
 The problem was that `assertQuerysetEqual` is dependant on the order of
 results, and with no explicit ordering applied the results were different
 in postgresql. I've updated the tests (and also fixed another typo I
 missed earlier) and rerun the lookup tests on sqlite, postgresql and
 mysql.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14439: Improve documentation on how to run the GIS test suite

[Django]

#14439: Improve documentation on how to run the GIS test suite
+---
  Reporter:  lukeplant  | Owner:  nobody
Status:  reopened   | Milestone:
 Component:  GIS|   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by jbronn):

 As of r14653, you no longer need a project settings file.  The following
 will suffice for a settings file:
 {{{
 #!python
 TEST_RUNNER='django.contrib.gis.tests.GeoDjangoTestSuiteRunner'

 DATABASES = {
 'default': {
 'ENGINE': 'django.contrib.gis.db.backends.postgis',
 'NAME': 'geodjango',
 'USER': 'geodjango',
 },
 }
 }}}

 In other words, if the above were in a file called `postgis.py`, then
 `django-admin.py test --settings=postgis` would run the !GeoDjango test
 suite.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14740: CZ Localflavor clean() incorrectly calls parent __init__

[Django]

#14740: CZ Localflavor clean() incorrectly calls parent __init__
-+--
  Reporter:  anonymous   | Owner:  nobody
Status:  closed  | Milestone:
 Component:  django.contrib.localflavor  |   Version:  1.2   
Resolution:  duplicate   |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by Alex):

  * status:  new => closed
  * needs_better_patch:  => 0
  * resolution:  => duplicate
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 Closing as a dupe of #14741

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #14741: CZ Localflavor clean() incorrectly calls parent __init__

[Django]

#14741: CZ Localflavor clean() incorrectly calls parent __init__
+---
 Reporter:  idangazit   |   Owner:  nobody
   Status:  new |   Milestone:
Component:  django.contrib.localflavor  | Version:  1.2   
 Keywords:  |   Stage:  Unreviewed
Has_patch:  1   |  
+---
 In cz/forms.py, see
 
[http://code.djangoproject.com/browser/django/trunk/django/contrib/localflavor/cz/forms.py#L54
 L54] and
 
[http://code.djangoproject.com/browser/django/trunk/django/contrib/localflavor/cz/forms.py#L111
 L111]. At the beginning of `clean()`, the parent's `__init__` is called
 instead of `clean()`.

 Patch attached. Discovered while converting doctests to unittests.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #14740: CZ Localflavor clean() incorrectly calls parent __init__

[Django]

#14740: CZ Localflavor clean() incorrectly calls parent __init__
+---
 Reporter:  anonymous   |   Owner:  nobody
   Status:  new |   Milestone:
Component:  django.contrib.localflavor  | Version:  1.2   
 Keywords:  |   Stage:  Unreviewed
Has_patch:  1   |  
+---
 In cz/forms.py, see
 
[http://code.djangoproject.com/browser/django/trunk/django/contrib/localflavor/cz/forms.py#L54
 L54] and
 
[http://code.djangoproject.com/browser/django/trunk/django/contrib/localflavor/cz/forms.py#L111
 L111]. At the beginning of `clean()`, the parent's `__init__` is called
 instead of `clean()`.

 Patch attached. Discovered while converting doctests to unittests.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Changeset] r14654 - django/branches/releases/1.2.X/django/contrib/gis/tests

[noreply]

Author: jbronn
Date: 2010-11-20 17:57:01 -0600 (Sat, 20 Nov 2010)
New Revision: 14654

Modified:
   django/branches/releases/1.2.X/django/contrib/gis/tests/__init__.py
Log:
[1.2.X] Now possible to run the GeoDjango test suite with a minimal settings 
file.  Refs #10420, #14439.

Backport of r14653 from trunk.

Modified: django/branches/releases/1.2.X/django/contrib/gis/tests/__init__.py
===
--- django/branches/releases/1.2.X/django/contrib/gis/tests/__init__.py 
2010-11-20 23:54:59 UTC (rev 14653)
+++ django/branches/releases/1.2.X/django/contrib/gis/tests/__init__.py 
2010-11-20 23:57:01 UTC (rev 14654)
@@ -29,8 +29,9 @@
 
 # Getting and storing the original values of INSTALLED_APPS and
 # the ROOT_URLCONF.
-self.old_installed = settings.INSTALLED_APPS
-self.old_root_urlconf = settings.ROOT_URLCONF
+self.old_installed = getattr(settings, 'INSTALLED_APPS', None)
+self.old_root_urlconf = getattr(settings, 'ROOT_URLCONF', None)
+self.old_site_id = getattr(settings, 'SITE_ID', None)
 
 # Tests that require use of a spatial database (e.g., creation of 
models)
 self.geo_apps = ['geoapp', 'relatedapp']
@@ -61,11 +62,13 @@
 
 # Setting the URLs.
 settings.ROOT_URLCONF = 'django.contrib.gis.tests.urls'
+settings.SITE_ID = 1
 
 def teardown_test_environment(self, **kwargs):
 super(GeoDjangoTestSuiteRunner, 
self).teardown_test_environment(**kwargs)
 settings.INSTALLED_APPS = self.old_installed
 settings.ROOT_URLCONF = self.old_root_urlconf
+settings.SITE_ID = self.old_site_id
 
 def build_suite(self, test_labels, extra_tests=None, **kwargs):
 """

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Changeset] r14653 - django/trunk/django/contrib/gis/tests

[noreply]

Author: jbronn
Date: 2010-11-20 17:54:59 -0600 (Sat, 20 Nov 2010)
New Revision: 14653

Modified:
   django/trunk/django/contrib/gis/tests/__init__.py
Log:
Now possible to run the GeoDjango test suite with a minimal settings file.  
Refs #10420, #14439.

Modified: django/trunk/django/contrib/gis/tests/__init__.py
===
--- django/trunk/django/contrib/gis/tests/__init__.py   2010-11-20 21:00:41 UTC 
(rev 14652)
+++ django/trunk/django/contrib/gis/tests/__init__.py   2010-11-20 23:54:59 UTC 
(rev 14653)
@@ -30,8 +30,9 @@
 
 # Getting and storing the original values of INSTALLED_APPS and
 # the ROOT_URLCONF.
-self.old_installed = settings.INSTALLED_APPS
-self.old_root_urlconf = settings.ROOT_URLCONF
+self.old_installed = getattr(settings, 'INSTALLED_APPS', None)
+self.old_root_urlconf = getattr(settings, 'ROOT_URLCONF', None)
+self.old_site_id = getattr(settings, 'SITE_ID', None)
 
 # Tests that require use of a spatial database (e.g., creation of 
models)
 self.geo_apps = ['geoapp', 'relatedapp']
@@ -62,11 +63,13 @@
 
 # Setting the URLs.
 settings.ROOT_URLCONF = 'django.contrib.gis.tests.urls'
+settings.SITE_ID = 1
 
 def teardown_test_environment(self, **kwargs):
 super(GeoDjangoTestSuiteRunner, 
self).teardown_test_environment(**kwargs)
 settings.INSTALLED_APPS = self.old_installed
 settings.ROOT_URLCONF = self.old_root_urlconf
+settings.SITE_ID = self.old_site_id
 
 def build_suite(self, test_labels, extra_tests=None, **kwargs):
 """

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #9964: Transaction middleware closes the transaction only when it's marked as dirty

[Django]

#9964: Transaction middleware closes the transaction only when it's marked as
dirty
---+
  Reporter:  ishirav   | Owner:  
mtredinnick 
Status:  assigned  | Milestone:  1.3
 
 Component:  Database layer (models, ORM)  |   Version:  1.0-beta-1 
 
Resolution:|  Keywords:  
transactions
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by shai):

  * needs_docs:  1 => 0

Comment:

 The patch I just uploaded adds to the previous version only documentation
 (text for release notes) and a single test. As far as I'm concerned, and
 pending comments saying otherwise, this is now ready for checkin.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #14739: Segregate contrib.localflavor translations to their ownPO file/gettext domain?

[Django]

#14739: Segregate contrib.localflavor translations to their ownPO file/gettext
domain?
--+-
 Reporter:  ramiro|   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Internationalization  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 In this way we could have, in a sense, more useful/realistic translation
 coverage stats. If we have N localflavors, every translator needs to take
 care of translating city, zone, district, tax IDs, etc. of these N
 countries to his/her own language. I suspect it is rarely used, if at all.

 As a translator, I'd like to know that I can get a Django core translation
 to/near 100% even if I don't get to or don't want to translate all literal
 of some recently added localflavor and I'm ok with the original strings
 added by the localflavor author being used instead. It would be useful to
 know that if I have 20% of missing translation on my 'main'
 ``django.po``file, they aren't localflavor translations but rather core,
 forms, or admin ones.

 One data point: Currently localflavor strings represent 48% of the French
 django.po, for example.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Changeset] r14652 - django/trunk/docs/_ext

[noreply]

Author: Alex
Date: 2010-11-20 15:00:41 -0600 (Sat, 20 Nov 2010)
New Revision: 14652

Modified:
   django/trunk/docs/_ext/djangodocs.py
Log:
Reformated some code for readability.

Modified: django/trunk/docs/_ext/djangodocs.py
===
--- django/trunk/docs/_ext/djangodocs.py2010-11-20 20:40:16 UTC (rev 
14651)
+++ django/trunk/docs/_ext/djangodocs.py2010-11-20 21:00:41 UTC (rev 
14652)
@@ -234,12 +234,12 @@
 return
 self.info(bold("writing templatebuiltins.js..."))
 xrefs = self.env.domaindata["std"]["objects"]
-templatebuiltins = dict([('ttags', [n for ((t,n), (l,a)) in 
xrefs.items()
-if t == 'templatetag' and
-l == 'ref/templates/builtins' ]),
- ('tfilters', [n for ((t,n), (l,a)) in 
xrefs.items()
-   if t == 'templatefilter' and
-   t == 
'ref/templates/builtins'])])
+templatebuiltins = {
+"ttags": [n for ((t, n), (l, a)) in xrefs.items()
+if t == "templatetag" and l == 
"ref/templates/builtins"],
+"tfilters": [n for ((t, n), (l, a)) in xrefs.items()
+if t == "templatefilter" and l == 
"ref/templates/builtins"],
+}
 outfilename = os.path.join(self.outdir, "templatebuiltins.js")
 f = open(outfilename, 'wb')
 f.write('var django_template_builtins = ')

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Changeset] r14651 - django/trunk/docs/ref

[noreply]

Author: lukeplant
Date: 2010-11-20 14:40:16 -0600 (Sat, 20 Nov 2010)
New Revision: 14651

Modified:
   django/trunk/docs/ref/class-based-views.txt
Log:
Fixed typo in docs.

Modified: django/trunk/docs/ref/class-based-views.txt
===
--- django/trunk/docs/ref/class-based-views.txt 2010-11-20 20:38:52 UTC (rev 
14650)
+++ django/trunk/docs/ref/class-based-views.txt 2010-11-20 20:40:16 UTC (rev 
14651)
@@ -779,7 +779,7 @@
 ``object_list`` is the list of objects ``extra_context`` is a
 dictionary of context data that will be added to any context data
 provided by the
-:class:`~django.db.views.generic.list.MultiplObjectMixin`.
+:class:`~django.views.generic.list.MultipleObjectMixin`.
 
 .. method:: get_dated_queryset(**lookup)
 

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Changeset] r14650 - in django/trunk: django/views/generic docs/topics

[noreply]

Author: lukeplant
Date: 2010-11-20 14:38:52 -0600 (Sat, 20 Nov 2010)
New Revision: 14650

Modified:
   django/trunk/django/views/generic/list_detail.py
   django/trunk/docs/topics/generic-views-migration.txt
Log:
Documented migration path for change object_list -> ListView regarding 
different context variables

Modified: django/trunk/django/views/generic/list_detail.py
===
--- django/trunk/django/views/generic/list_detail.py2010-11-20 11:33:43 UTC 
(rev 14649)
+++ django/trunk/django/views/generic/list_detail.py2010-11-20 20:38:52 UTC 
(rev 14650)
@@ -71,10 +71,10 @@
 '%s_list' % template_object_name: page_obj.object_list,
 'paginator': paginator,
 'page_obj': page_obj,
+'is_paginated': page_obj.has_other_pages(),
 
 # Legacy template context stuff. New templates should use page_obj
 # to access this instead.
-'is_paginated': page_obj.has_other_pages(),
 'results_per_page': paginator.per_page,
 'has_next': page_obj.has_next(),
 'has_previous': page_obj.has_previous(),

Modified: django/trunk/docs/topics/generic-views-migration.txt
===
--- django/trunk/docs/topics/generic-views-migration.txt2010-11-20 
11:33:43 UTC (rev 14649)
+++ django/trunk/docs/topics/generic-views-migration.txt2010-11-20 
20:38:52 UTC (rev 14650)
@@ -74,6 +74,26 @@
 variable name. In a class-based ``ListView``, the
 ``context_object_name`` is used verbatim.
 
+The context data for ``object_list`` views
+--
+
+The context provided by :class:`~django.views.generic.list.MultipleObjectMixin`
+is quite different from that provided by ``object_list``, with most pagination
+related variables replaced by a single ``page_obj`` object. The following are 
no
+longer provided:
+
+* ``first_on_page``
+* ``has_next``
+* ``has_previous``
+* ``hits``
+* ``last_on_page``
+* ``next``
+* ``page_range``
+* ``page``
+* ``pages``
+* ``previous``
+* ``results_per_page``
+
 ``extra_context``
 -
 

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14738: Link settings in cache doc to settings reference, for consistency.

[Django]

#14738: Link settings in cache doc to settings reference, for consistency.
+---
  Reporter:  adamv  | Owner:  nobody
Status:  new| Milestone:  1.3   
 Component:  Documentation  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by jezdez):

  * needs_better_patch:  => 0
  * needs_docs:  => 0
  * stage:  Unreviewed => Ready for checkin
  * needs_tests:  => 0
  * milestone:  => 1.3

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #13860: Translate the output of admin commands

[Django]

#13860: Translate the output of admin commands
---+
  Reporter:  tonnzor   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Internationalization  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by SmileyChris):

  * summary:  Translate admin commands => Translate the output of admin
  commands
  * stage:  Design decision needed => Accepted

Comment:

 Oh, right - I think I got confused between translating the output and
 translating the commands themselves.

 Yes, translating the output seems fine.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #13860: Translate admin commands

[Django]

#13860: Translate admin commands
-+--
  Reporter:  tonnzor | Owner:  nobody
Status:  new | Milestone:
 Component:  Internationalization|   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by claudep):

 Replying to [comment:7 SmileyChris]:
 > Most command line utilities don't translate their arguments.

 You're probably wrong here. At least most of GNOME command line utilities
 are translating their 'usage' output.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #3529: Context.update doesn't do what it says it does

[Django]

#3529: Context.update doesn't do what it says it does
+---
  Reporter:  SmileyChris| Owner:  ggetzie
Status:  assigned   | Milestone: 
 Component:  Documentation  |   Version:  SVN
Resolution: |  Keywords: 
 Stage:  Accepted   | Has_patch:  1  
Needs_docs:  1  |   Needs_tests:  0  
Needs_better_patch:  1  |  
+---
Changes (by SmileyChris):

  * needs_better_patch:  0 => 1

Comment:

 I'd like to see the documentation have a separate block which explains the
 Context.update behaviour -- it's likely to get overlooked otherwise.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #3529: Context.update doesn't do what it says it does

[Django]

#3529: Context.update doesn't do what it says it does
+---
  Reporter:  SmileyChris| Owner:  ggetzie
Status:  assigned   | Milestone: 
 Component:  Documentation  |   Version:  SVN
Resolution: |  Keywords: 
 Stage:  Accepted   | Has_patch:  1  
Needs_docs:  1  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by ggetzie):

  * has_patch:  0 => 1

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #13860: Translate admin commands

[Django]

#13860: Translate admin commands
-+--
  Reporter:  tonnzor | Owner:  nobody
Status:  new | Milestone:
 Component:  Internationalization|   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by SmileyChris):

  * stage:  Accepted => Design decision needed

Comment:

 Actually, I'm not so sure this is a good idea. Most command line utilities
 don't translate their arguments and I'm not sure we should either. Bring
 this up in the django developers group.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #3529: Context.update doesn't do what it says it does

[Django]

#3529: Context.update doesn't do what it says it does
+---
  Reporter:  SmileyChris| Owner:  ggetzie
Status:  assigned   | Milestone: 
 Component:  Documentation  |   Version:  SVN
Resolution: |  Keywords: 
 Stage:  Accepted   | Has_patch:  0  
Needs_docs:  1  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by SmileyChris):

  * component:  Template system => Documentation

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #3529: Context.update doesn't do what it says it does

[Django]

#3529: Context.update doesn't do what it says it does
--+-
  Reporter:  SmileyChris  | Owner:  ggetzie
Status:  assigned | Milestone: 
 Component:  Template system  |   Version:  SVN
Resolution:   |  Keywords: 
 Stage:  Accepted | Has_patch:  0  
Needs_docs:  1|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by ggetzie):

  * owner:  nobody => ggetzie
  * status:  new => assigned

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14417: UnicodeDecodeError exception in recent actions

[Django]

#14417: UnicodeDecodeError exception in recent actions
---+
  Reporter:  ctetruite | Owner:  nobody 
Status:  new   | Milestone: 
 Component:  django.contrib.admin  |   Version:  1.2
Resolution:|  Keywords:  unicode
 Stage:  Unreviewed| Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Comment (by claudep):

 I've just added a test that specifically tests this. But on my system, it
 passes without your patch.

 Why would entry.content_type.name not be an Unicode string in the first
 place?

 The following snippet could indicate you if ContentType names are really
 all Unicode strings.
 {{{
 from django.contrib.contenttypes.models import ContentType
 for c in ContentType.objects.all():
 print c.name.__class__, c.name
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #14738: Link settings in cache doc to settings reference, for consistency.

[Django]

#14738: Link settings in cache doc to settings reference, for consistency.
---+
 Reporter:  adamv  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 This patch link settings in cache doc to settings reference, and links
 CACHE_ settings back to the cache docs, for consistency.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #14737: Move doc comment for "cache_page" to function.

[Django]

#14737: Move doc comment for "cache_page" to function.
--+-
 Reporter:  adamv |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Cache system  | Version:  1.2   
 Keywords:|   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 The doc comment for "cache_page" was hanging out at the top of the module,
 instead of the targeted function.

 This patch moves the doc comment down to the function.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12158: Strange Swedish translation of "Go"

[Django]

#12158: Strange Swedish translation of "Go"
+---
  Reporter:  skorpan| Owner:  nobody
Status:  new| Milestone:
 Component:  Translations   |   Version:  SVN   
Resolution: |  Keywords:  i18n swedish admin
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by claudep):

  * stage:  Accepted => Ready for checkin

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12158: Strange Swedish translation of "Go"

[Django]

#12158: Strange Swedish translation of "Go"
---+
  Reporter:  skorpan   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Translations  |   Version:  SVN   
Resolution:|  Keywords:  i18n swedish admin
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by claudep):

  * has_patch:  0 => 1

Comment:

 I've got confirmation by a Swedish translation expert (Daniel Nylander)
 that:

 ''"Utför" is the best in this specific context. It means "Perform" or
 "Do" (the action)''

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14284: Support for Google Maps version 3

[Django]

#14284: Support for Google Maps version 3
+---
  Reporter:  DaveWP196  | Owner:  ericpalakovichcarr
Status:  assigned   | Milestone:
 Component:  GIS|   Version:  1.2   
Resolution: |  Keywords:  Google Maps   
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by ericpalakovichcarr):

  * owner:  nobody => ericpalakovichcarr
  * status:  new => assigned

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #14736: Typo in documentation

[Django]

#14736: Typo in documentation
---+
 Reporter:  DD |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.2   
 Keywords:  typo   |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Hello

 I just wanted to let you know that there is a typo in the "Built-in
 template tags and filters" section, under filter "add".

 C/P from the page:


 Warning

 Keep in mind '''that strings that can both be coerced to integers will be,
 and thus will be will be summed''',[[BR]]
 not concatenated, as in the first example above.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14637: There may an Internationalization bug in Forms

[Django]

#14637: There may an Internationalization bug in Forms
-+--
  Reporter:  thefm...@gmail.com  | Owner:  nobody  
Status:  closed  | Milestone:  
 Component:  Translations|   Version:  1.2 
Resolution:  invalid |  Keywords:  Internationalization
 Stage:  Unreviewed  | Has_patch:  0   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by claudep):

  * status:  new => closed
  * resolution:  => invalid

Comment:

 I confirm this is due to the Chinese translation not being up-to-date.
 This is not a bug per se.

 I encourage you to work on improving Chinese translation for Django (see
 also http://docs.djangoproject.com/en/1.2/topics/i18n/localization/).

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #13860: Translate admin commands

[Django]

#13860: Translate admin commands
---+
  Reporter:  tonnzor   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Internationalization  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by lrekucki):

  * stage:  Someday/Maybe => Accepted

Comment:

 I'll switch this to Accepted, because I think it's a good idea.

 There is actually no need to read the settings.LANGUAGE_CODE - django-
 admin.py is command line tool, so it should probably just take the locale
 from environment. The OP did note that his fine with only translating help
 texts (and possibly error messages, but that's a bit of problem),  but
 leaving command names in English.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #13860: Translate admin commands

[Django]

#13860: Translate admin commands
---+
  Reporter:  tonnzor   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Internationalization  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Someday/Maybe | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by claudep):

  * component:  Translations => Internationalization

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14730: Translation Mistake. MN

[Django]

#14730: Translation Mistake. MN
---+
  Reporter:  ankhbayar | Owner:  nobody
Status:  new   | Milestone:
 Component:  Translations  |   Version:  1.2   
Resolution:|  Keywords:  MN
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by claudep):

  * stage:  Unreviewed => Accepted

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14586: Make interpolate JS function not require the named parameter.

[Django]

#14586: Make interpolate JS function not require the named parameter.
---+
  Reporter:  aminland  | Owner:  nobody
Status:  new   | Milestone:  1.3   
 Component:  Internationalization  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by claudep):

  * needs_better_patch:  => 0
  * component:  Translations => Internationalization
  * needs_tests:  => 0
  * needs_docs:  => 0

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14174: Support for string interpolation in lazy translation

[Django]

#14174: Support for string interpolation in lazy translation
-+--
  Reporter:  zimnyx  | Owner:  nobody
Status:  new | Milestone:
 Component:  Internationalization|   Version:  1.2   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by claudep):

  * component:  Translations => Internationalization
  * stage:  Unreviewed => Design decision needed

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14735: Wrong plural formulation in search_form.html

[Django]

#14735: Wrong plural formulation in search_form.html
---+
  Reporter:  claudep   | Owner:  claudep
Status:  new   | Milestone:  1.3
 Component:  django.contrib.admin  |   Version:  1.2
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Comment (by claudep):

 I looked at current translations, and my opinion is that we should not
 backport this fix, as it will break translations for a rather visible
 string and I doubt we have the required knowledge to guess the right
 change in various languages (64!).
 I'm adding a second patch which includes fixes for Chinese translations,
 as the required changes to make them msgfmt -vc compliant are trivial. I
 let the committer decide if he wants to include translation fixes in the
 same commit or not.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14733: Allow Manager.raw() execute not only "Pure selects"

[Django]

#14733: Allow Manager.raw() execute not  only "Pure selects"
---+
  Reporter:  dzentoo   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Comment (by dzentoo):

 Well, I tried "sqlparse" without success ..

 {{{
 res = sqlparse.parse("(SELECT * FROM pouet LIMIT 5) UNION (SELECT * FROM
 repouet)")
 st = res[0]
 print st.get_type()
 'UNKNOWN'
 }}}

 What If I match if the query does not contain UPDATE / INSERT / DELETE ?
 what do you mean by 'flexible validation' ? Any idea on how you 'll
 proceed ?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14733: Allow Manager.raw() execute not only "Pure selects"

[Django]

#14733: Allow Manager.raw() execute not  only "Pure selects"
---+
  Reporter:  dzentoo   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Comment (by russellm):

 It's not a security measure -- it's a matter of basic functionality. The
 rest of the behavior of raw() deals with converting the returned results
 into Django objects. The query validation is purely about ensuring that
 the query will actually return results that can be converted into Django
 objects.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14733: Allow Manager.raw() execute not only "Pure selects"

[Django]

#14733: Allow Manager.raw() execute not  only "Pure selects"
---+
  Reporter:  dzentoo   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Comment (by kemar):

 Why are raw queries strictly limited to SELECT queries? Is this a security
 measure?
 Seems like determining whether a query is a SELECT or not require a
 complex regex.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14735: Wrong plural formulation in search_form.html

[Django]

#14735: Wrong plural formulation in search_form.html
---+
  Reporter:  claudep   | Owner:  claudep
Status:  new   | Milestone:  1.3
 Component:  django.contrib.admin  |   Version:  1.2
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by jezdez):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * needs_tests:  => 0
  * needs_docs:  => 0

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #14735: Wrong plural formulation in search_form.html

[Django]

#14735: Wrong plural formulation in search_form.html
--+-
 Reporter:  claudep   |   Owner:  claudep   
   Status:  new   |   Milestone:  1.3   
Component:  django.contrib.admin  | Version:  1.2   
 Keywords:|   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 In search_form.html template from contrib.admin, the singular of the
 search results message is using a number (1) instead of the variable:
 {{{
   {% blocktrans count cl.result_count as counter %}1 result{% plural %}{{
 counter }} results{% endblocktrans %}
 }}}

 This is fine in English, but is causing issues in languages where the
 singular might be used with more than one number, like 0 and 1 for French.
 Fix is trivial and requires using {{ counter }} in singular form also.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Changeset] r14649 - django/trunk/docs/topics

[noreply]

Author: russellm
Date: 2010-11-20 05:33:43 -0600 (Sat, 20 Nov 2010)
New Revision: 14649

Modified:
   django/trunk/docs/topics/class-based-views.txt
Log:
Corrected a markup problem with an example in the class-based view docs. Thanks 
to apollo13 for the report.

Modified: django/trunk/docs/topics/class-based-views.txt
===
--- django/trunk/docs/topics/class-based-views.txt  2010-11-20 11:16:43 UTC 
(rev 14648)
+++ django/trunk/docs/topics/class-based-views.txt  2010-11-20 11:33:43 UTC 
(rev 14649)
@@ -579,7 +579,7 @@
 you can't just apply a function decorator to the method -- you need to
 transform it into a method decorator first. The ``method_decorator``
 decorator transforms a function decorator into a method decorator so
-that it can be used on an instance method.
+that it can be used on an instance method. For example::
 
 from django.contrib.auth.decorators import login_required
 from django.utils.decorators import method_decorator

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Changeset] r14648 - django/trunk/docs/ref/templates

[noreply]

Author: russellm
Date: 2010-11-20 05:16:43 -0600 (Sat, 20 Nov 2010)
New Revision: 14648

Modified:
   django/trunk/docs/ref/templates/builtins.txt
Log:
Corrected a typo in the docs for {% load %}. Thanks to Jannis for the report.

Modified: django/trunk/docs/ref/templates/builtins.txt
===
--- django/trunk/docs/ref/templates/builtins.txt2010-11-20 11:11:39 UTC 
(rev 14647)
+++ django/trunk/docs/ref/templates/builtins.txt2010-11-20 11:16:43 UTC 
(rev 14648)
@@ -662,7 +662,7 @@
 
 {% load somelibrary otherlibrary %}
 
-You can also selectively load individual templates or tags from a library, 
using
+You can also selectively load individual filters or tags from a library, using
 the ``from`` argument. In this example, the template tags/filters named ``foo``
 and ``bar`` will be loaded from ``somelibrary``::
 

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Changeset] r14647 - django/branches/releases/1.2.X/docs/ref/contrib/admin

[noreply]

Author: gabrielhurley
Date: 2010-11-20 05:11:39 -0600 (Sat, 20 Nov 2010)
New Revision: 14647

Modified:
   django/branches/releases/1.2.X/docs/ref/contrib/admin/admindocs.txt
Log:
[1.2.X] Replaced an unnecessary UTF8 character in the admindocs docs. Thanks to 
Luke Plant for the report.

Backport of [14646] from trunk.

Modified: django/branches/releases/1.2.X/docs/ref/contrib/admin/admindocs.txt
===
--- django/branches/releases/1.2.X/docs/ref/contrib/admin/admindocs.txt 
2010-11-20 11:10:48 UTC (rev 14646)
+++ django/branches/releases/1.2.X/docs/ref/contrib/admin/admindocs.txt 
2010-11-20 11:11:39 UTC (rev 14647)
@@ -131,7 +131,7 @@
 While ``admindocs`` does not include a place to document templates by
 themselves, if you use the ``:template:`path/to/template.html``` syntax in a
 docstring the resulting page will verify the path of that template with
-Django’s :ref:`template loaders `. This can be a handy way to
+Django's :ref:`template loaders `. This can be a handy way to
 check if the specified template exists and to show where on the filesystem that
 template is stored.
 

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Changeset] r14646 - django/trunk/docs/ref/contrib/admin

[noreply]

Author: gabrielhurley
Date: 2010-11-20 05:10:48 -0600 (Sat, 20 Nov 2010)
New Revision: 14646

Modified:
   django/trunk/docs/ref/contrib/admin/admindocs.txt
Log:
Replaced an inappropriate UTF8 character in the admindocs docs. Thanks to Luke 
Plant for the report.

Modified: django/trunk/docs/ref/contrib/admin/admindocs.txt
===
--- django/trunk/docs/ref/contrib/admin/admindocs.txt   2010-11-20 10:51:04 UTC 
(rev 14645)
+++ django/trunk/docs/ref/contrib/admin/admindocs.txt   2010-11-20 11:10:48 UTC 
(rev 14646)
@@ -131,7 +131,7 @@
 While ``admindocs`` does not include a place to document templates by
 themselves, if you use the ``:template:`path/to/template.html``` syntax in a
 docstring the resulting page will verify the path of that template with
-Django’s :ref:`template loaders `. This can be a handy way to
+Django's :ref:`template loaders `. This can be a handy way to
 check if the specified template exists and to show where on the filesystem that
 template is stored.
 

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #3094: XMLField not working (and it shouldn't require Jing; should use other tools if available.)

[Django]

#3094: XMLField not working (and it shouldn't require Jing; should use other 
tools
if available.)
-+--
  Reporter:  goliath.mailingl...@gmx.de  | Owner:  jacob

Status:  new | Milestone:   

 Component:  Validators  |   Version:  SVN  

Resolution:  |  Keywords:  relaxng 
validator
 Stage:  Accepted| Has_patch:  1

Needs_docs:  1   |   Needs_tests:  0

Needs_better_patch:  1   |  
-+--
Comment (by masaki):

 I was one of the few Japanese Python programmer.
 I have Django with Web development is, I'm embarrassed by the Japanese
 XMLField little information.
 I was poor reading English, so would you please translate into Japanese?

 私は数少ない日本のPythonプログラマーです。
 私はDjangoによるWeb開発を進めているのですが、日本語のXMLFieldの情報が少ないので困ってます。
 私は英語が下手なので、日本語に翻訳して頂けますか?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14712: Example for post_syncdb signal.

[Django]

#14712: Example for post_syncdb signal.
+---
  Reporter:  frankwiles | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by gabrielhurley):

  * stage:  Unreviewed => Accepted

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Changeset] r14645 - in django/branches/releases/1.2.X/docs/topics: db http

[noreply]

Author: gabrielhurley
Date: 2010-11-20 04:51:04 -0600 (Sat, 20 Nov 2010)
New Revision: 14645

Modified:
   django/branches/releases/1.2.X/docs/topics/db/optimization.txt
   django/branches/releases/1.2.X/docs/topics/http/file-uploads.txt
   django/branches/releases/1.2.X/docs/topics/http/urls.txt
Log:
[1.2.X] Fixed #14727 -- Corrected three minor issues in the docs. Thanks to 
OldTroll for the report and the patch.

Backport of [14644] from trunk.

Modified: django/branches/releases/1.2.X/docs/topics/db/optimization.txt
===
--- django/branches/releases/1.2.X/docs/topics/db/optimization.txt  
2010-11-20 10:49:42 UTC (rev 14644)
+++ django/branches/releases/1.2.X/docs/topics/db/optimization.txt  
2010-11-20 10:51:04 UTC (rev 14645)
@@ -4,7 +4,7 @@
 
 Django's database layer provides various ways to help developers get the most
 out of their databases. This document gathers together links to the relevant
-documentation, and adds various tips, organized under an number of headings 
that
+documentation, and adds various tips, organized under a number of headings that
 outline the steps to take when attempting to optimize your database usage.
 
 Profile first

Modified: django/branches/releases/1.2.X/docs/topics/http/file-uploads.txt
===
--- django/branches/releases/1.2.X/docs/topics/http/file-uploads.txt
2010-11-20 10:49:42 UTC (rev 14644)
+++ django/branches/releases/1.2.X/docs/topics/http/file-uploads.txt
2010-11-20 10:51:04 UTC (rev 14645)
@@ -363,8 +363,7 @@
 ``'image/jpeg'``.
 
 ``content_length`` is the length of the image given by the browser.
-Sometimes this won't be provided and will be ``None``., ``None``
-otherwise.
+Sometimes this won't be provided and will be ``None``.
 
 ``charset`` is the character set (i.e. ``utf8``) given by the browser.
 Like ``content_length``, this sometimes won't be provided.

Modified: django/branches/releases/1.2.X/docs/topics/http/urls.txt
===
--- django/branches/releases/1.2.X/docs/topics/http/urls.txt2010-11-20 
10:49:42 UTC (rev 14644)
+++ django/branches/releases/1.2.X/docs/topics/http/urls.txt2010-11-20 
10:51:04 UTC (rev 14645)
@@ -809,7 +809,7 @@
 namespaces into URLs on specific application instances, according to the
 :ref:`namespaced URL resolution strategy 
`.
 
-.. admonition:: Make sure your views are all correct
+.. admonition:: Make sure your views are all correct.
 
 As part of working out which URL names map to which patterns, the
 ``reverse()`` function has to import all of your URLconf files and examine

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Changeset] r14644 - in django/trunk/docs/topics: db http

[noreply]

Author: gabrielhurley
Date: 2010-11-20 04:49:42 -0600 (Sat, 20 Nov 2010)
New Revision: 14644

Modified:
   django/trunk/docs/topics/db/optimization.txt
   django/trunk/docs/topics/http/file-uploads.txt
   django/trunk/docs/topics/http/urls.txt
Log:
Fixed #14727 -- Corrected three minor issues in the docs. Thanks to OldTroll 
for the report and the patch.

Modified: django/trunk/docs/topics/db/optimization.txt
===
--- django/trunk/docs/topics/db/optimization.txt2010-11-20 06:22:28 UTC 
(rev 14643)
+++ django/trunk/docs/topics/db/optimization.txt2010-11-20 10:49:42 UTC 
(rev 14644)
@@ -4,7 +4,7 @@
 
 Django's database layer provides various ways to help developers get the most
 out of their databases. This document gathers together links to the relevant
-documentation, and adds various tips, organized under an number of headings 
that
+documentation, and adds various tips, organized under a number of headings that
 outline the steps to take when attempting to optimize your database usage.
 
 Profile first

Modified: django/trunk/docs/topics/http/file-uploads.txt
===
--- django/trunk/docs/topics/http/file-uploads.txt  2010-11-20 06:22:28 UTC 
(rev 14643)
+++ django/trunk/docs/topics/http/file-uploads.txt  2010-11-20 10:49:42 UTC 
(rev 14644)
@@ -363,8 +363,7 @@
 ``'image/jpeg'``.
 
 ``content_length`` is the length of the image given by the browser.
-Sometimes this won't be provided and will be ``None``., ``None``
-otherwise.
+Sometimes this won't be provided and will be ``None``.
 
 ``charset`` is the character set (i.e. ``utf8``) given by the browser.
 Like ``content_length``, this sometimes won't be provided.

Modified: django/trunk/docs/topics/http/urls.txt
===
--- django/trunk/docs/topics/http/urls.txt  2010-11-20 06:22:28 UTC (rev 
14643)
+++ django/trunk/docs/topics/http/urls.txt  2010-11-20 10:49:42 UTC (rev 
14644)
@@ -809,7 +809,7 @@
 namespaces into URLs on specific application instances, according to the
 :ref:`namespaced URL resolution strategy 
`.
 
-.. admonition:: Make sure your views are all correct
+.. admonition:: Make sure your views are all correct.
 
 As part of working out which URL names map to which patterns, the
 ``reverse()`` function has to import all of your URLconf files and examine

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #13312: order_by on null-field gives different results on different db engines

[Django]

#13312: order_by on null-field gives different results on different db engines
---+
  Reporter:  binary| Owner:  nobody 
 
Status:  closed| Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  1.1
 
Resolution:  wontfix   |  Keywords:  ordering, 
order_by, null
 Stage:  Unreviewed| Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by chexum):

  * keywords:  ordering, order_by => ordering, order_by, null

Comment:

 Just to document it, there is a very easy way to control this behavior.
 The most portable seems to be an additional order by for "field IS NULL".
 It puts NULLs last in at least sqlite3, mysql and PostgreSQL.  The reverse
 is either "field IS NULL DESC" or "field IS NOT NULL".

 It's also easy to use in a Django way:

 {{{
 q = q.extra(select={'null1':'field1 is null','null2':'field2 is
 null'})
 q = q.extra(order_by=['null1','-field1','-null2','field2'])
 }}}

 Because it's so easy to do in a standard way, it might be worth at some
 point to add a specific queryset for it (not necessarily modifying
 order_by()), as extra() is not always desirable.   Having a new queryset
 would allow backend specific optimization, like nulls last/first if
 supported.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.