Re: [Django] #8317: inspectdb does not set primary_key=True or unique=True on foreign keys

[Django]

#8317: inspectdb does not set primary_key=True or unique=True on foreign keys
-+-
 Reporter:  bthomas  |Owner:  dgouldin
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  SVN
  commands)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  inspectdb|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by julien):

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


Comment:

 In [17451]:
 {{{
 #!CommitTicketReference repository="" revision="17451"
 Fixed #8317 -- Corrected the inspectdb management command to properly set
 `primary_key=True` and `unique=True` on foreign keys. Thanks to bthomas
 for the report and patch, and to David Gouldin for the tests.
 }}}

-- 
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-updates@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] r17451 - in django/trunk: django/core/management/commands tests/regressiontests/inspectdb

[noreply]

Author: julien
Date: 2012-02-04 23:51:37 -0800 (Sat, 04 Feb 2012)
New Revision: 17451

Modified:
   django/trunk/django/core/management/commands/inspectdb.py
   django/trunk/tests/regressiontests/inspectdb/models.py
   django/trunk/tests/regressiontests/inspectdb/tests.py
Log:
Fixed #8317 -- Corrected the inspectdb management command to properly set 
`primary_key=True` and `unique=True` on foreign keys. Thanks to bthomas for the 
report and patch, and to David Gouldin for the tests.

Modified: django/trunk/django/core/management/commands/inspectdb.py
===
--- django/trunk/django/core/management/commands/inspectdb.py   2012-02-05 
07:11:53 UTC (rev 17450)
+++ django/trunk/django/core/management/commands/inspectdb.py   2012-02-05 
07:51:37 UTC (rev 17451)
@@ -62,15 +62,22 @@
 if ' ' in att_name or '-' in att_name or 
keyword.iskeyword(att_name) or column_name != att_name:
 extra_params['db_column'] = column_name
 
+# Add primary_key and unique, if necessary.
+if column_name in indexes:
+if indexes[column_name]['primary_key']:
+extra_params['primary_key'] = True
+elif indexes[column_name]['unique']:
+extra_params['unique'] = True
+
 # Modify the field name to make it Python-compatible.
 if ' ' in att_name:
 att_name = att_name.replace(' ', '_')
 comment_notes.append('Field renamed to remove spaces.')
-
+
 if '-' in att_name:
 att_name = att_name.replace('-', '_')
 comment_notes.append('Field renamed to remove dashes.')
-
+
 if column_name != att_name:
 comment_notes.append('Field name made lowercase.')
 
@@ -88,15 +95,8 @@
 extra_params.update(field_params)
 comment_notes.extend(field_notes)
 
-# Add primary_key and unique, if necessary.
-if column_name in indexes:
-if indexes[column_name]['primary_key']:
-extra_params['primary_key'] = True
-elif indexes[column_name]['unique']:
-extra_params['unique'] = True
+field_type += '('
 
-field_type += '('
-
 if keyword.iskeyword(att_name):
 att_name += '_field'
 comment_notes.append('Field renamed because it was a 
Python reserved word.')

Modified: django/trunk/tests/regressiontests/inspectdb/models.py
===
--- django/trunk/tests/regressiontests/inspectdb/models.py  2012-02-05 
07:11:53 UTC (rev 17450)
+++ django/trunk/tests/regressiontests/inspectdb/models.py  2012-02-05 
07:51:37 UTC (rev 17451)
@@ -6,3 +6,12 @@
 
 class Message(models.Model):
 from_field = models.ForeignKey(People, db_column='from_id')
+
+class PeopleData(models.Model):
+people_pk = models.ForeignKey(People, primary_key=True)
+ssn = models.CharField(max_length=11)
+
+class PeopleMoreData(models.Model):
+people_unique = models.ForeignKey(People, unique=True)
+license = models.CharField(max_length=255)
+

Modified: django/trunk/tests/regressiontests/inspectdb/tests.py
===
--- django/trunk/tests/regressiontests/inspectdb/tests.py   2012-02-05 
07:11:53 UTC (rev 17450)
+++ django/trunk/tests/regressiontests/inspectdb/tests.py   2012-02-05 
07:51:37 UTC (rev 17451)
@@ -13,4 +13,8 @@
 error_message = "inspectdb generated an attribute name which is a 
python keyword"
 self.assertNotIn("from = models.ForeignKey(InspectdbPeople)", 
out.getvalue(), msg=error_message)
 self.assertIn("from_field = models.ForeignKey(InspectdbPeople)", 
out.getvalue())
+self.assertIn("people_pk = models.ForeignKey(InspectdbPeople, 
primary_key=True)",
+out.getvalue())
+self.assertIn("people_unique = models.ForeignKey(InspectdbPeople, 
unique=True)",
+out.getvalue())
 out.close()

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@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] r17450 - in django/trunk: django/db/models/sql tests/modeltests/lookup

[noreply]

Author: julien
Date: 2012-02-04 23:11:53 -0800 (Sat, 04 Feb 2012)
New Revision: 17450

Modified:
   django/trunk/django/db/models/sql/query.py
   django/trunk/tests/modeltests/lookup/models.py
   django/trunk/tests/modeltests/lookup/tests.py
Log:
Fixed #11670 -- Prevented genuine model fields named 'year', 'month', 'gt', 
'lt' etc. from being mistaken for lookup types in lookups across relations. 
Thanks to andy for the report, to jpwatts for the initial patch and to Anssi 
Ka?\204?\136a?\204?\136ria?\204?\136inen and Alex Gaynor for the reviews.

Modified: django/trunk/django/db/models/sql/query.py
===
--- django/trunk/django/db/models/sql/query.py  2012-02-04 22:12:58 UTC (rev 
17449)
+++ django/trunk/django/db/models/sql/query.py  2012-02-05 07:11:53 UTC (rev 
17450)
@@ -1061,11 +1061,31 @@
 if not parts:
 raise FieldError("Cannot parse keyword query %r" % arg)
 
-# Work out the lookup type and remove it from 'parts', if necessary.
-if len(parts) == 1 or parts[-1] not in self.query_terms:
-lookup_type = 'exact'
-else:
-lookup_type = parts.pop()
+# Work out the lookup type and remove it from the end of 'parts',
+# if necessary.
+lookup_type = 'exact' # Default lookup type
+num_parts = len(parts)
+if (len(parts) > 1 and parts[-1] in self.query_terms
+and arg not in self.aggregates):
+# Traverse the lookup query to distinguish related fields from
+# lookup types.
+lookup_model = self.model
+for counter, field_name in enumerate(parts):
+try:
+lookup_field = lookup_model._meta.get_field(field_name)
+except FieldDoesNotExist:
+# Not a field. Bail out.
+lookup_type = parts.pop()
+break
+# Unless we're at the end of the list of lookups, let's attempt
+# to continue traversing relations.
+if (counter + 1) < num_parts:
+try:
+lookup_model = lookup_field.rel.to
+except AttributeError:
+# Not a related field. Bail out.
+lookup_type = parts.pop()
+break
 
 # By default, this is a WHERE clause. If an aggregate is referenced
 # in the value, the filter will be promoted to a HAVING

Modified: django/trunk/tests/modeltests/lookup/models.py
===
--- django/trunk/tests/modeltests/lookup/models.py  2012-02-04 22:12:58 UTC 
(rev 17449)
+++ django/trunk/tests/modeltests/lookup/models.py  2012-02-05 07:11:53 UTC 
(rev 17450)
@@ -27,3 +27,25 @@
 name = models.CharField(max_length=100)
 class Meta:
 ordering = ('name', )
+
+class Season(models.Model):
+year = models.PositiveSmallIntegerField()
+gt = models.IntegerField(null=True, blank=True)
+
+def __unicode__(self):
+return unicode(self.year)
+
+class Game(models.Model):
+season = models.ForeignKey(Season, related_name='games')
+home = models.CharField(max_length=100)
+away = models.CharField(max_length=100)
+
+def __unicode__(self):
+return u"%s at %s" % (self.away, self.home)
+
+class Player(models.Model):
+name = models.CharField(max_length=100)
+games = models.ManyToManyField(Game, related_name='players')
+
+def __unicode__(self):
+return self.name
\ No newline at end of file

Modified: django/trunk/tests/modeltests/lookup/tests.py
===
--- django/trunk/tests/modeltests/lookup/tests.py   2012-02-04 22:12:58 UTC 
(rev 17449)
+++ django/trunk/tests/modeltests/lookup/tests.py   2012-02-05 07:11:53 UTC 
(rev 17450)
@@ -1,4 +1,4 @@
-from __future__ import absolute_import
+from __future__ import absolute_import, with_statement
 
 from datetime import datetime
 from operator import attrgetter
@@ -6,12 +6,11 @@
 from django.core.exceptions import FieldError
 from django.test import TestCase, skipUnlessDBFeature
 
-from .models import Author, Article, Tag
+from .models import Author, Article, Tag, Game, Season, Player
 
 
 class LookupTests(TestCase):
 
-#def setUp(self):
 def setUp(self):
 # Create a few Authors.
 self.au1 = Author(name='Author 1')
@@ -610,3 +609,80 @@
 a16.save()
 
self.assertQuerysetEqual(Article.objects.filter(headline__regex=r'b(.).*b\1'),
 ['', '', ''])
+
+def test_nonfield_lookups(self):
+"""
+Ensure that a lookup query containing non-fields raises the proper
+exception.
+"""
+with self.assertRaises(FieldError):
+Article.objects.filter(headline__blahblah=99)
+with self.assertRaises(FieldError)

Re: [Django] #11670: Model fields named 'year', 'month', 'gt', 'lt' etc. get mistaken for lookup types in lookups across relations

[Django]

#11670: Model fields named 'year', 'month', 'gt', 'lt' etc. get mistaken for 
lookup
types in lookups across relations
-+-
 Reporter:  andy@…   |Owner:  julien
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  SVN
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by julien):

 * status:  new => closed
 * owner:   => julien
 * resolution:   => fixed


Comment:

 In [17450]:
 {{{
 #!CommitTicketReference repository="" revision="17450"
 Fixed #11670 -- Prevented genuine model fields named 'year', 'month',
 'gt', 'lt' etc. from being mistaken for lookup types in lookups across
 relations. Thanks to andy for the report, to jpwatts for the initial patch
 and to Anssi Kääriäinen and Alex Gaynor for the reviews.
 }}}

-- 
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-updates@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] #11670: Model fields named 'year', 'month', 'gt', 'lt' etc. get mistaken for lookup types in lookups across relations

[Django]

#11670: Model fields named 'year', 'month', 'gt', 'lt' etc. get mistaken for 
lookup
types in lookups across relations
-+-
 Reporter:  andy@…   |Owner:
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  SVN
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by julien):

 I'm going to commit the fix for the originally reported issue. A deeper
 refactoring would still be welcome but it should be tackled as part of a
 separate ticket. #16187 could be a good candidate.

-- 
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-updates@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] #17648: Allow `ContentTypeManager` and `GenericForeignKey` to retreive/store proxy model content type.

[Django]

#17648: Allow `ContentTypeManager` and `GenericForeignKey` to retreive/store 
proxy
model content type.
-+-
 Reporter:  charettes|Owner:  charettes
 Type:  Bug  |   Status:  new
Component:   |  Version:  SVN
  contrib.contenttypes   |   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:  contenttype proxy|  decision needed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by danny.adair@…):

 * cc: danny.adair@… (added)


-- 
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-updates@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] #17647: Documentation Bug: override_settings() not in 1.30

[Django]

#17647: Documentation Bug: override_settings() not in 1.30
---+--
 Reporter:  glen@… |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.3
 Severity:  Normal |   Resolution:  invalid
 Keywords:  override_settings  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by mattmcc):

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


Comment:

 The documentation page you reference is not for 1.3, it's the development
 docs.  The equivalent page for 1.3 is
 https://docs.djangoproject.com/en/1.3/topics/testing/ which indeed does
 not mention override_settings.

-- 
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-updates@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] #11154: Inconsistency with permissions for proxy models

[Django]

#11154: Inconsistency with permissions for proxy models
--+
 Reporter:  etianen   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by charettes):

 Ticket #17648 fixes this issue (see attached path there). I finally agree
 that this is nothing but a bug that was introduced back in r10523 for
 ticket #10738.

-- 
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-updates@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] #17648: Allow `ContentTypeManager` and `GenericForeignKey` to retreive/store proxy model content type.

[Django]

#17648: Allow `ContentTypeManager` and `GenericForeignKey` to retreive/store 
proxy
model content type.
-+-
 Reporter:  charettes|Owner:  charettes
 Type:  Bug  |   Status:  new
Component:   |  Version:  SVN
  contrib.contenttypes   |   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:  contenttype proxy|  decision needed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * cc: charette.s@… (added)
 * has_patch:  0 => 1
 * 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-updates@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] #17648: Allow `ContentTypeManager` and `GenericForeignKey` to retreive/store proxy model content type.

[Django]

#17648: Allow `ContentTypeManager` and `GenericForeignKey` to retreive/store 
proxy
model content type.
-+-
 Reporter:  charettes|Owner:  charettes
 Type:  Bug  |   Status:  new
Component:   |  Version:  SVN
  contrib.contenttypes   |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  contenttype proxy|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * needs_better_patch:   => 0
 * type:  New feature => Bug
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Marking as bug since I really believe it was mistakenly introduced by
 r10523.

-- 
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-updates@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] #17648: Allow `ContentTypeManager` and `GenericForeignKey` to retreive/store proxy model content type.

[Django]

#17648: Allow `ContentTypeManager` and `GenericForeignKey` to retreive/store 
proxy
model content type.
--+---
 Reporter:  charettes |  Owner:  charettes
 Type:  New feature   | Status:  new
Component:  contrib.contenttypes  |Version:  SVN
 Severity:  Normal|   Keywords:  contenttype proxy
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+---
 The actual `ContentTypeManager`'s `get_for_model` and `get_for_models`
 methods always return the `ContentType` of the concrete class of a proxy
 model. This behaviour is causing `GenericForeignKey` to save the concrete
 class of proxy model and creates inconsistencies in the
 `ContentTypeManager`'s `get_...` API:
 {{{
 from django.contrib.auth.models import User
 from django.contrib.contenttypes.models import ContentType

 class Worker(User):
 class Meta:
   app_label = 'app'
   proxy = True

 ct_get_for_model = ContentType.objects.get_for_model(Worker)
 ct_natural_key = ContentType.objects.get_by_natural_key('app', 'worker')
 assert ct_natural_key == ct_get_for_model # raises AssertionError
 }}}

 I don't know if it was a design decision (IHMO it's a mistake and a bug)
 to do so but changing it now would introduce a small backward
 compatibility issue for any app relying on `get_for_model` directly or
 indirectly through the use of `GenericForeignKey' since they would now
 ''benefit'' from getting the exact ct they were referencing.

 If I'm not mistaken, by looking at
 
[https://github.com/charettes/django/blob/master/tests/regressiontests/defer_regress/tests.py#L65-71
 regressiontests.defer_regress.tests.DeferRegressionTest] and #10738, I
 assume this was introduced by r10523 to make sure deferred models are
 handled correctly by `get_for_model`. Checks for proxy reversing should be
 made against `model._defered` and not `model._meta.proxy'.

 A discussion recently emerged of #11154 (which is caused by this
 behaviour) suggesting to either remove the proxy following routine of
 `get_for_model(s?)` or to allow passing a flag (`follow_proxy`) to ''opt-
 in'' for the ''correct'' behaviour.

 I'm attaching a simple patch that only replaces the checks in `_get_opts`
 (and automatically fixes #11154) and I'll be marking the ticket as 'DDN'
 since it involves a small backward compatibility issue that requires
 feedbac.

-- 
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-updates@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] #11154: Inconsistency with permissions for proxy models

[Django]

#11154: Inconsistency with permissions for proxy models
--+
 Reporter:  etianen   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by charettes):

 Replying to [comment:38 danny.adair@…]:
 > Replying to [comment:37 charettes]:
 > >[...]
 > > Defaulting {{{ follow_proxy }}} (like that one :) to `False` would
 unify both API but would break backward compatibility.
 > >[...]
 > > I ran the test with {{{ follow_proxy=False }}} as default and only
 [http://dpaste.com/hold/697615/ two tests breaks]. However apps relying on
 `contrib.ContentType` in the wild could break badly.
 > > [...]
 > > We can either break the API to unite them or offer the user to ''opt-
 in'' in order to maintain backward compatibility. But this whole
 discussion is getting bigger then the ticket itself. We should maybe open
 another issue to fix the `ContentType` proxy issue that blocks this one
 and then, once it's fixed, use the new hooks to fix this one with:
 >
 > I agree an implementation in two steps would help everyone (and faster
 to get checked in).
 > Just want to point out that if you consider this a bug (like I do) then
 backwards-compatibility (= keep software happy that relies on the bug) is
 a less strong argument for retaining it. Right the wrong or continue its
 adoption? django-reversion is _currently_ broken.
 I'm in the process of writing a new ticket describing the issue in which
 I'll suggest a design decision is taken toward breaking backward
 compatibility.

-- 
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-updates@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] #17647: Documentation Bug: override_settings() not in 1.30

[Django]

#17647: Documentation Bug: override_settings() not in 1.30
---+---
 Reporter:  glen@… |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  1.3
 Severity:  Normal |   Keywords:  override_settings
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+---
 According to the documentation for Django 1.3 (confirmed Django 1.3 in
 'Version' drop down box on page load):

 https://docs.djangoproject.com/en/dev/topics/testing/

 In case you want to override a setting for just one test method or even
 the whole TestCase class, Django provides the override_settings()
 decorator (see PEP 318). It's used like this:
 ...
 from django.test.utils import override_settings

 However, this is not available in 1.3


 {{{
 (glenjarvis)Pokey.local> ./manage.py shell
 Python 2.6.1 (r261:67515, Aug  2 2010, 20:10:18)
 [GCC 4.2.1 (Apple Inc. build 5646)] on darwin
 Type "help", "copyright", "credits" or "license" for more information.
 (InteractiveConsole)
 >>> import django
 >>> print django.VERSION
 (1, 3, 0, 'final', 0)
 >>> from django.test.utils import override_settings
 Traceback (most recent call last):
   File "", line 1, in 
 ImportError: cannot import name override_settings
 }}}

 I have verified, however, that this is available in 1.4 Alpha:
 {{{
 (django14)Pokey.local> python manage.py shell
 Python 2.6.1 (r261:67515, Aug  2 2010, 20:10:18)
 [GCC 4.2.1 (Apple Inc. build 5646)] on darwin
 Type "help", "copyright", "credits" or "license" for more information.
 (InteractiveConsole)
 >>> import django
 >>> print django.VERSION
 (1, 4, 0, 'alpha', 1)
 >>> from django.test.utils import override_settings
 >>>
 }}}

 Therefore, this is just a documentation error for version.

-- 
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-updates@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] #11154: Inconsistency with permissions for proxy models

[Django]

#11154: Inconsistency with permissions for proxy models
--+
 Reporter:  etianen   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by danny.adair@…):

 Replying to [comment:37 charettes]:
 >[...]
 > Defaulting {{{ follow_proxy }}} (like that one :) to `False` would unify
 both API but would break backward compatibility.
 >[...]
 > I ran the test with {{{ follow_proxy=False }}} as default and only
 [http://dpaste.com/hold/697615/ two tests breaks]. However apps relying on
 `contrib.ContentType` in the wild could break badly.
 > [...]
 > We can either break the API to unite them or offer the user to ''opt-
 in'' in order to maintain backward compatibility. But this whole
 discussion is getting bigger then the ticket itself. We should maybe open
 another issue to fix the `ContentType` proxy issue that blocks this one
 and then, once it's fixed, use the new hooks to fix this one with:

 I agree an implementation in two steps would help everyone (and faster to
 get checked in).
 Just want to point out that if you consider this a bug (like I do) then
 backwards-compatibility (= keep software happy that relies on the bug) is
 a less strong argument for retaining it. Right the wrong or continue its
 adoption? django-reversion is _currently_ broken.

-- 
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-updates@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] #11154: Inconsistency with permissions for proxy models

[Django]

#11154: Inconsistency with permissions for proxy models
--+
 Reporter:  etianen   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by charettes):

 Replying to [comment:36 danny.adair@…]:
 > follow_proxy, traverse_proxy? (or even _proxies)
 >
 > The default behaviour would still be "broken" - !ModelBase and
 !ContentManager would still be giving different stories regarding
 app_label
 Defaulting {{{ follow_proxy }}} (like that one :) to `False` would unify
 both API but would break backward compatibility.

 I ran the test with {{{ follow_proxy=False }}} as default and only
 [http://dpaste.com/hold/697615/ two tests breaks]. However apps relying on
 `contrib.ContentType` in the wild could break badly.

 i.e. ([https://github.com/alex/django-taggit django-taggit]) If you
 defined a `TaggableManager()` (uses `GenericForeignKey` internally) on a
 proxy model then all tags will be associated with the concrete model
 `ContentType` in the db. If we release `follow_proxy=False` as default
 then the generic relation between the proxy model and the tags will be
 broken since they were never associated with the proxy's ct.

 We can either break the API to unite them or offer the user to ''opt-in''
 in order to maintain backward compatibility. But this whole issue is
 bigger then the ticket itself. We should maybe open another issue to fix
 the `ContentType` proxy issue that blocks this one and then, once it's
 fixed, use the new hooks to fix this one with:

 {{{
 diff --git a/django/contrib/auth/management/__init__.py
 b/django/contrib/auth/management/__init__.py
 index 78a51cf..a1d2d9e 100644
 --- a/django/contrib/auth/management/__init__.py
 +++ b/django/contrib/auth/management/__init__.py
 @@ -31,7 +31,8 @@ def create_permissions(app, created_models, verbosity,
 **kwargs):
  searched_perms = list()
  # The codenames and ctypes that should exist.
  ctypes = set()
 -ctypes_for_models = ContentType.objects.get_for_models(*app_models)
 +ctypes_for_models = ContentType.objects.get_for_models(*app_models,
 +
 follow_proxy=False)
  for klass, ctype in ctypes_for_models.iteritems():
  ctypes.add(ctype)
  for perm in _get_all_permissions(klass._meta):
 }}}

-- 
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-updates@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] #17379: Silent translation of all ./manage.py commands to en-us unexpected/undocumented

[Django]

#17379: Silent translation of all ./manage.py commands to en-us
unexpected/undocumented
-+-
 Reporter:  chrischambers|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  SVN
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  management, shell,   |  Needs documentation:  1
  i18n, l10n, en-us, translation,|  Patch needs improvement:  1
  documentation  |UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  1|
-+-

Comment (by ramiro):

 I'd like to ask to the contributors working on this ticket what are the
 practical consequences (as in concrete use cases) for the 'shell'and
 'makemessages' of being run always with the en-us locale.

 It is not clear to me why both of them are particular among the rest of
 the commands and IMHO having that information would be helpful when it
 comes to solve/re-triage this ticket.

-- 
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-updates@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] #16964: FileField files can't be opened in write mode if not closed before

[Django]

#16964: FileField files can't be opened in write mode if not closed before
--+
 Reporter:  jonash|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  File uploads/storage  |  Version:  1.3
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by anonymous):

 already has tests, what's missing?

-- 
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-updates@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] #11154: Inconsistency with permissions for proxy models

[Django]

#11154: Inconsistency with permissions for proxy models
--+
 Reporter:  etianen   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by danny.adair@…):

 follow_proxy, traverse_proxy? (or even _proxies)

 The default behaviour would still be "broken" - !ModelBase and
 !ContentManager would still be giving different stories regarding
 app_label

-- 
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-updates@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] #15124: BooleanField should not use False as default (unless provided)

[Django]

#15124: BooleanField should not use False as default (unless provided)
-+-
 Reporter:  andrewbadr   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |  1.4-alpha-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  1
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by ethlinn):

 * cc: asendecka@… (added)
 * needs_docs:  0 => 1
 * version:  1.3-beta => 1.4-alpha-1
 * stage:  Accepted => Ready for checkin


Comment:

 Works ok. Tests and docs are there, so RFC.

-- 
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-updates@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] #17631: edge case: django.test.client should handle fields and files with the same name

[Django]

#17631: edge case: django.test.client should handle fields and files with the 
same
name
---+
 Reporter:  dnozay |Owner:  lrekucki
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.3
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by lrekucki):

 * owner:  nobody => lrekucki
 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * 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-updates@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] #17645: runserver: not serving static for localhost

[Django]

#17645: runserver: not serving static for localhost
-+-
 Reporter:  shadow   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  SVN
  commands)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by shadow):

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


Comment:

 Actually, now that I think about it... there won't be an easy way of
 knowing whether the domain is pointing to 127.0.0.1 or not. So this
 probably can't be fixed reliably.

 Never mind :]

-- 
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-updates@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] #17646: Create a get_list_filter hook in ModelAdmin

[Django]

#17646: Create a get_list_filter hook in ModelAdmin
---+--
 Reporter:  rasca  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  SVN
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by rasca):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Maybe also creating hooks for all the remaining ModelAdmin properties.

-- 
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-updates@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] #17646: Create a get_list_filter hook in ModelAdmin

[Django]

#17646: Create a get_list_filter hook in ModelAdmin
---+
 Reporter:  rasca  |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  contrib.admin  |Version:  SVN
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 This would be useful when for example the queryset is filtered based on a
 user type and the superuser can see all types. For a superuser one could
 add a the type field to list_display and list_filter.

-- 
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-updates@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] #17636: InMemoryUploadedFile object has no attribute _committed

[Django]

#17636: InMemoryUploadedFile object has no attribute _committed
-+-
 Reporter:  lwarx|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  File |  Version:  1.3
  uploads/storage|   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by lrekucki):

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


Comment:

 AFAIK, you should only use {{{SubfieldBase}}} if you're subclassing
 {{{Field}}} itself. See the notes on subclassing {{{FileField}}}
 (https://docs.djangoproject.com/en/dev/howto/custom-model-
 fields/#writing-a-filefield-subclass) for a better way to do what you
 want.

-- 
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-updates@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] #17375: 'makemessages' ignores plural from 'blocktrans'

[Django]

#17375: 'makemessages' ignores plural from 'blocktrans'
-+-
 Reporter:  ahagenbruch  |Owner:  pigletto
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  SVN
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by ext):

 * stage:  Accepted => Ready for checkin


Comment:

 Looks and works OK.

-- 
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-updates@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] #17436: flag attempts to change signature of __init__ on Models

[Django]

#17436: flag attempts to change signature of __init__ on Models
--+
 Reporter:  straz |Owner:  zsiciarz
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.3
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by zsiciarz):

 * 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-updates@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] #17632: new filter for localflavor 'The Netherlands'

[Django]

#17632: new filter for localflavor 'The Netherlands'
-+
 Reporter:  lkeijser |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.localflavor  |  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by lrekucki):

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


Old description:

> I've created a small filter that can be used in the same way as
> 'pluralize'. It basically adds 'en' (most common pluralized word in
> Dutch) when used.
>
> '''
> from django import template
> from django.template.defaultfilters import stringfilter
>
> register = template.Library()
>
> @register.filter
> def meervoud(value, arg=u'en'):
> if not u',' in arg:
> arg = u',' + arg
> bits = arg.split(u',')
> if len(bits) > 2:
> return u''
> singular_suffix, plural_suffix = bits[:2]
>
> try:
> if int(value) != 1:
> return plural_suffix
> except ValueError: # Invalid string that's not a number.
> pass
> except TypeError: # Value isn't a string or a number; maybe it's a
> list?
> try:
> if len(value) != 1:
> return plural_suffix
> except TypeError: # len() of unsized object.
> pass
> return singular_suffix
> '''

New description:

 I've created a small filter that can be used in the same way as
 'pluralize'. It basically adds 'en' (most common pluralized word in Dutch)
 when used.

 {{{#!python
 from django import template
 from django.template.defaultfilters import stringfilter

 register = template.Library()

 @register.filter
 def meervoud(value, arg=u'en'):
 if not u',' in arg:
 arg = u',' + arg
 bits = arg.split(u',')
 if len(bits) > 2:
 return u''
 singular_suffix, plural_suffix = bits[:2]

 try:
 if int(value) != 1:
 return plural_suffix
 except ValueError: # Invalid string that's not a number.
 pass
 except TypeError: # Value isn't a string or a number; maybe it's a
 list?
 try:
 if len(value) != 1:
 return plural_suffix
 except TypeError: # len() of unsized object.
 pass
 return singular_suffix
 }}}

--

Comment:

 Please provide this in a form of a patch (diff against current Django
 trunk) attached to the ticket. Also, every new feature needs both tests
 and documentation. I'm not Dutch so I can't really speak about usefulness
 of this.

-- 
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-updates@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] #17645: runserver: not serving static for localhost

[Django]

#17645: runserver: not serving static for localhost
-+-
 Reporter:  shadow   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  SVN
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by shadow):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Sorry, that fix should be:

 {{{
 def _should_handle(self, path):
 return path.startswith(self.base_url[2])

 }}}

-- 
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-updates@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] #17637: Client side validation classes for forms

[Django]

#17637: Client side validation classes for forms
-+-
 Reporter:  karthikabinav|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:  Forms , Client Side  | Triage Stage:  Accepted
  validation, js |  Needs documentation:  1
Has patch:  0|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  1
Easy pickings:  0|
-+-
Changes (by lrekucki):

 * 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-updates@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] #17637: Client side validation classes for forms

[Django]

#17637: Client side validation classes for forms
-+-
 Reporter:  karthikabinav|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:  Forms , Client Side  | Triage Stage:
  validation, js |  Unreviewed
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-
Changes (by lrekucki):

 * needs_docs:   => 1
 * needs_tests:   => 1
 * needs_better_patch:   => 1


Old description:

> Having client side javascript validation for forms having common fields
> like username having only alphanumerics or password and Confirm password
> fields matching by providing a validation class.
>
> For example a user should be able to do something like :
>
> forms.TextField(validators ="usernameValidation")
>
>  And automatically a javascript validation for this form field should be
> in place.
>
> One way to do it could be using HTML5 attributes like ticket #16304.

New description:

 Having client side javascript validation for forms having common fields
 like username having only alphanumerics or password and Confirm password
 fields matching by providing a validation class.

 For example a user should be able to do something like :

 {{{
 forms.TextField(validators ="usernameValidation")
 }}}

 And automatically a javascript validation for this form field should be in
 place.

 One way to do it could be using HTML5 attributes like ticket #16304.

--

Comment:

 Per discussion on django-developers, I think we can accept this on
 principal (not the patch itself, as it doesn't have tests or docs). IMHO,
 best approach would be to use HTML5 features + provide some simple
 JavaScript fallback for not widely supported features.

-- 
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-updates@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] #1453: generic views sometimes inefficient with large data sets - especially archive_index

[Django]

#1453: generic views sometimes inefficient with large data sets - especially
archive_index
---+-
 Reporter:  hugo   |Owner:  zefciu
 Type:  New feature|   Status:  assigned
Component:  Generic views  |  Version:
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Someday/Maybe
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by zefciu):

 * has_patch:  0 => 1


Comment:

 I have created a patch that makes `date_list` in both class-based and
 function-based views lazy. Also created some tests to check the behavior
 of function-based `archive-index` (there were none before) and to ensure
 `date_list` is a `Promise`

-- 
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-updates@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] #17375: 'makemessages' ignores plural from 'blocktrans'

[Django]

#17375: 'makemessages' ignores plural from 'blocktrans'
--+
 Reporter:  ahagenbruch   |Owner:  pigletto
 Type:  Bug   |   Status:  assigned
Component:  Internationalization  |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by pigletto):

 Uploaded issue_17375.2.diff that uses --files-from parameter for xgettext.
 Now patch seems to be complete for me.

-- 
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-updates@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] #17638: Link up topic guides with API reference

[Django]

#17638: Link up topic guides with API reference
---+
 Reporter:  oinopion   |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  SVN
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by lrekucki):

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


Comment:

 Can't hurt.

-- 
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-updates@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] #17645: runserver: not serving static for localhost

[Django]

#17645: runserver: not serving static for localhost
+
 Reporter:  shadow  |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Core (Management commands)  |Version:  SVN
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  1   |  UI/UX:  0
+
 runserver will only serve static files if STATIC_URL is relative. This
 makes sense if STATIC_URL includes a domain pointing to another server.
 However, it denies the possibility of including a localhost domain (as is
 needed by my current project).

 I've currently worked around this by modifying:
 django/contrib/staticfiles/handlers.py


 {{{
 def _should_handle(self, path):
 return True
 }}}


 Sorry, I haven't had time to consider any side effects of this, but it's
 working for me at the moment.

-- 
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-updates@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] #17642: min_num on admin inline formsets

[Django]

#17642: min_num on admin inline formsets
-+-
 Reporter:   |Owner:  nobody
  krzysztof.szczesny@…   |   Status:  new
 Type:  New feature  |  Version:
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  admin min_num|  Needs documentation:  0
  formsets   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  1
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by lrekucki):

 * 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-updates@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] #14786: get_db_prep_lookup call get_prep_value twice for each value if prepared == False

[Django]

#14786: get_db_prep_lookup call get_prep_value twice for each value if prepared 
==
False
-+-
 Reporter:  homm |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  SVN
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  sprintdec2010|  Needs documentation:  0
  fields lookup  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by lrekucki):

 * needs_better_patch:  1 => 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-updates@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] #17138: Admin sets the "summary" attribute on table, which is obsolete

[Django]

#17138: Admin sets the "summary" attribute on table, which is obsolete
-+-
 Reporter:  aaugustin|Owner:  teraom
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  SVN
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by claudep):

 I'm not sure this is ready. Summary attribute was not displayed by default
 in browsers, while caption tag is. I'm not sure we suddenly want to
 display the summary content.

-- 
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-updates@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] #17390: Describe how to do auth for Class Based Views in the main Auth docs

[Django]

#17390: Describe how to do auth for Class Based Views in the main Auth docs
-+-
 Reporter:  ncoghlan@…   |Owner:  zsiciarz
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.3
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by ethlinn):

 * cc: asendecka@… (added)
 * stage:  Accepted => Ready for checkin


Comment:

 I think it's ok.

-- 
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-updates@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] #17436: flag attempts to change signature of __init__ on Models

[Django]

#17436: flag attempts to change signature of __init__ on Models
--+
 Reporter:  straz |Owner:  zsiciarz
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.3
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by zsiciarz):

 * owner:  nobody => zsiciarz


-- 
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-updates@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] #17390: Describe how to do auth for Class Based Views in the main Auth docs

[Django]

#17390: Describe how to do auth for Class Based Views in the main Auth docs
--+
 Reporter:  ncoghlan@…|Owner:  zsiciarz
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.3
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by zsiciarz):

 * 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-updates@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] #15906: New head method needs documentation

[Django]

#15906: New head method needs documentation
---+
 Reporter:  jezdez |Owner:  zsiciarz
 Type:  Bug|   Status:  new
Component:  Generic views  |  Version:  1.3
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by zsiciarz):

 * 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-updates@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] #12583: Postgresql backend uses implicit text casts for case insensitive operators

[Django]

#12583: Postgresql backend uses implicit text casts for case insensitive 
operators
-+-
 Reporter:  Ubercore |Owner:  Ubercore
 Type:  Bug  |   Status:  reopened
Component:  Database layer   |  Version:  SVN
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  postgresql cast  |  Needs documentation:  0
  case-insensitive   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by kwadrat):

 Waiting 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-updates@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] r17449 - django/trunk/django/core/management/commands

[noreply]

Author: ramiro
Date: 2012-02-04 14:12:58 -0800 (Sat, 04 Feb 2012)
New Revision: 17449

Modified:
   django/trunk/django/core/management/commands/makemessages.py
Log:
Made a couple of idiomatic changes in makemessages.

Modified: django/trunk/django/core/management/commands/makemessages.py
===
--- django/trunk/django/core/management/commands/makemessages.py
2012-02-04 21:44:31 UTC (rev 17448)
+++ django/trunk/django/core/management/commands/makemessages.py
2012-02-04 22:12:58 UTC (rev 17449)
@@ -46,10 +46,12 @@
 return p.communicate()
 
 def walk(root, topdown=True, onerror=None, followlinks=False,
- ignore_patterns=[], verbosity=0, stdout=sys.stdout):
+ ignore_patterns=None, verbosity=0, stdout=sys.stdout):
 """
 A version of os.walk that can follow symlinks for Python < 2.6
 """
+if ignore_patterns is None:
+ignore_patterns = []
 dir_suffix = '%s*' % os.sep
 norm_patterns = map(lambda p: p.endswith(dir_suffix)
 and p[:-len(dir_suffix)] or p, ignore_patterns)
@@ -391,9 +393,10 @@
 no_location = options.get('no_location')
 no_obsolete = options.get('no_obsolete')
 if domain == 'djangojs':
-extensions = handle_extensions(extensions or ['js'])
+exts = extensions if extensions else ['js']
 else:
-extensions = handle_extensions(extensions or ['html', 'txt'])
+exts = extensions if extensions else ['html', 'txt']
+extensions = handle_extensions(exts)
 
 if verbosity > 1:
 self.stdout.write('examining files with the extensions: %s\n'

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@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] #14786: get_db_prep_lookup call get_prep_value twice for each value if prepared == False

[Django]

#14786: get_db_prep_lookup call get_prep_value twice for each value if prepared 
==
False
-+-
 Reporter:  homm |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  SVN
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  sprintdec2010|  Needs documentation:  0
  fields lookup  |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by lrekucki):

 * needs_better_patch:  0 => 1
 * ui_ux:   => 0
 * easy:   => 0


Old description:

> In db.models.fields.Field ''get_db_prep_lookup()'' check if value is
> prepared and prepare it:
> {{{
> def get_db_prep_lookup(self, lookup_type, value, connection,
> prepared=False):
> "Returns field's value prepared for database lookup."
> if not prepared:
> value = self.get_prep_lookup(lookup_type, value)
> }}}
> ''get_prep_lookup()'' call ''get_prep_value()'' for every value.
>
> But look next:
> {{{
> elif lookup_type in ('exact', 'gt', 'gte', 'lt', 'lte'):
> return [self.get_db_prep_value(value, connection=connection,
> prepared=prepared)]
> elif lookup_type in ('range', 'in'):
> return [self.get_db_prep_value(v, connection=connection,
> prepared=prepared) for v in value]
> }}}
> Prepared flag not changed and ''get_db_prep_value()'' call
> ''get_prep_value()'' through ''get_db_prep_value()'' again!
>
> I think ''get_db_prep_lookup()'' should call ''get_db_prep_value()''
> always with prepared == True.
> {{{
> elif lookup_type in ('exact', 'gt', 'gte', 'lt', 'lte'):
> return [self.get_db_prep_value(value, connection=connection,
> prepared=True)]
> elif lookup_type in ('range', 'in'):
> return [self.get_db_prep_value(v, connection=connection,
> prepared=True) for v in value]
> }}}
>
> This bug is still unnoticed because in standard ORM
> ''get_db_prep_lookup()'' always calls with prepared == True.

New description:

 In db.models.fields.Field {{{get_db_prep_lookup()}}} check if value is
 prepared and prepare it:

 {{{#!python
 def get_db_prep_lookup(self, lookup_type, value, connection,
 prepared=False):
 "Returns field's value prepared for database lookup."
 if not prepared:
 value = self.get_prep_lookup(lookup_type, value)
 }}}
 {{{get_prep_lookup()}}} call {{{get_prep_value()}}} for every value.

 But look next:
 {{{#!python
 elif lookup_type in ('exact', 'gt', 'gte', 'lt', 'lte'):
 return [self.get_db_prep_value(value, connection=connection,
 prepared=prepared)]
 elif lookup_type in ('range', 'in'):
 return [self.get_db_prep_value(v, connection=connection,
 prepared=prepared) for v in value]
 }}}
 Prepared flag not changed and {{{get_db_prep_value()}}} call
 {{{get_prep_value()}}} through {{{get_db_prep_value()}}} again!

 I think {{{get_db_prep_lookup()}}} should call {{{get_db_prep_value()}}}
 always with {{{prepared == True}}}.
 {{{#!python
 elif lookup_type in ('exact', 'gt', 'gte', 'lt', 'lte'):
 return [self.get_db_prep_value(value, connection=connection,
 prepared=True)]
 elif lookup_type in ('range', 'in'):
 return [self.get_db_prep_value(v, connection=connection,
 prepared=True) for v in value]
 }}}

 This bug is still unnoticed because in standard ORM
 {{{get_db_prep_lookup()}}} always calls with {{{prepared == True}}}.

--

Comment:

 Patch doesn't apply cleanly, will try to rebase.

-- 
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-updates@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] #12583: Postgresql backend uses implicit text casts for case insensitive operators

[Django]

#12583: Postgresql backend uses implicit text casts for case insensitive 
operators
-+-
 Reporter:  Ubercore |Owner:  Ubercore
 Type:  Bug  |   Status:  reopened
Component:  Database layer   |  Version:  SVN
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  postgresql cast  |  Needs documentation:  0
  case-insensitive   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by kwadrat):

 * status:  closed => reopened
 * resolution:  fixed =>


-- 
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-updates@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] #15321: Models._get_unique_checks() does not return grandparents' unique checks

[Django]

#15321: Models._get_unique_checks() does not return grandparents' unique checks
-+-
 Reporter:  jku  |Owner:  sswang
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.2
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  models, unique   |  Needs documentation:  0
  checks |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by lrekucki):

 * needs_better_patch:  0 => 1
 * ui_ux:   => 0
 * easy:   => 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-updates@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] #11518: Custom commands cannot be run from cron (or other directory) if project is not on Python Path

[Django]

#11518: Custom commands cannot be run from cron (or other directory) if project 
is
not on Python Path
-+-
 Reporter:  mark.ellul@… |Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Core (Other) |  Version:
 Severity:  Normal   |  1.1-beta-1
 Keywords:  custom commands  |   Resolution:
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by lrekucki):

 * ui_ux:   => 0
 * easy:   => 0
 * stage:  Accepted => Ready for checkin


Comment:

 Looks good, although getting rid of the terrible hack on {{{PYTHON_PATH}}}
 would be even better.

-- 
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-updates@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] #10080: call_command doesn't take into account command's default options

[Django]

#10080: call_command doesn't take into account command's default options
-+-
 Reporter:  alexkoshelev |Owner:
 Type:  Bug  |  alexkoshelev
Component:  Core (Other) |   Status:  reopened
 Severity:  Normal   |  Version:  SVN
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by jezdez):

 * 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-updates@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] #15220: replace SelectFilter2.js with a jQuery plugin

[Django]

#15220: replace SelectFilter2.js with a jQuery plugin
-+-
 Reporter:  slurms   |Owner:  dbunskoek
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  SVN
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  1
Easy pickings:  0|
-+-

Comment (by jezdez):

 FWIW, selenium tests have now landed in the admin, so this should be much
 easier to test.

-- 
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-updates@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] #9433: File locking broken on AFP mounts

[Django]

#9433: File locking broken on AFP mounts
-+-
 Reporter:  rndblnch |Owner:  anonymous
 Type:  Bug  |   Status:  new
Component:  File |  Version:  1.1
  uploads/storage|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by lrekucki):

 * needs_better_patch:  0 => 1
 * ui_ux:   => 0
 * easy:   => 0


Comment:

 The patch doesn't apply (needs a very simple cleanup), but more
 importantly this needs checking if it's still a problem on OS X 10.7, etc.

-- 
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-updates@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] #15753: test_simple_sitemap fails after executing test_requestsite_sitemap when Sites app and FetchFromCacheMiddleware are installed.

[Django]

#15753: test_simple_sitemap fails after executing test_requestsite_sitemap when
Sites app and FetchFromCacheMiddleware are installed.
--+
 Reporter:  lucho |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.sitemaps  |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:  test  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

 * keywords:   => test
 * version:  1.3 => SVN


Comment:

 The problem is that in those tests, there are several requests for the
 same URL ('/simple/sitemap.xml', '/simple/sitemap-simple.xml'), so that's
 totally previsible that when caching is enabled, some already rendered
 contents are reused. The patch from lucho is one way to solve this.
 Another one would be to empty the cache just for the failing tests. A
 third approach would be to isolate the tests from unwanted middlewares
 (override_settings(MIDDLEWARE_CLASSES = ...).

-- 
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-updates@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] #17644: Use namedtuples in Query.alias_map to make debugging easier

[Django]

#17644: Use namedtuples in Query.alias_map to make debugging easier
-+-
 Reporter:  lrekucki |Owner:  lrekucki
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.3
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by Alex):

 * stage:  Unreviewed => Accepted


Comment:

 I'd much prefer waiting until we can use namedtuple comprehensively, and
 take advantage of the attribute syntax for items, so I'd rather wait for
 1.5 to do this.

-- 
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-updates@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] r17448 - django/trunk/django/core/management/commands

[noreply]

Author: ramiro
Date: 2012-02-04 13:44:31 -0800 (Sat, 04 Feb 2012)
New Revision: 17448

Modified:
   django/trunk/django/core/management/commands/makemessages.py
Log:
Removed hard-coded root tree path in makemessages.

Modified: django/trunk/django/core/management/commands/makemessages.py
===
--- django/trunk/django/core/management/commands/makemessages.py
2012-02-04 21:01:11 UTC (rev 17447)
+++ django/trunk/django/core/management/commands/makemessages.py
2012-02-04 21:44:31 UTC (rev 17448)
@@ -84,7 +84,7 @@
 Helper function to get all files in the given root.
 """
 all_files = []
-for (dirpath, dirnames, filenames) in walk(".", followlinks=symlinks,
+for (dirpath, dirnames, filenames) in walk(root, followlinks=symlinks,
 ignore_patterns=ignore_patterns, verbosity=verbosity, 
stdout=stdout):
 for filename in filenames:
 norm_filepath = os.path.normpath(os.path.join(dirpath, filename))

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@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] #17644: Use namedtuples in Query.alias_map to make debugging easier

[Django]

#17644: Use namedtuples in Query.alias_map to make debugging easier
-+-
 Reporter:  lrekucki |Owner:  lrekucki
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.3
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by lrekucki):

 * owner:  nobody => lrekucki
 * 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-updates@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] #16150: Syndication Feed docs incorrectly describe tag.

[Django]

#16150: Syndication Feed docs incorrectly describe  tag.
-+-
 Reporter:  melinath |Owner:  melinath
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:  rss  | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by jezdez):

 * 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-updates@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] #16416: date template tag should support "e" and "o" format character

[Django]

#16416: date template tag should support "e" and "o" format character
-+-
 Reporter:  CarstenF |Owner:  poirier
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:  ISO 8601 | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by jezdez):

 * 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-updates@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] #17644: Use namedtuples in Query.alias_map to make debugging easier

[Django]

#17644: Use namedtuples in Query.alias_map to make debugging easier
-+-
   Reporter:  lrekucki   |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |Version:  1.3
  Component:  Database   |   Keywords:
  layer (models, ORM)|  Has patch:  0
   Severity:  Normal |Needs tests:  0
   Triage Stage: |  Easy pickings:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 Debugging the SQL compiler is not an easy task, and having to keep track
 of values in 8-tuples doesn't make it easier ;) There are probably more
 places that this could be applied to, not just {{{alias_map}}}, but it's a
 start. {{{namedtuple}}} has no extra memory or performance overhead (I
 didn't notice any change in the runtime of testsuite).

 On Python 2.5, we just use a plain tuple (lookup code hasn't been changed
 so it just works).

-- 
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-updates@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] #17375: 'makemessages' ignores plural from 'blocktrans'

[Django]

#17375: 'makemessages' ignores plural from 'blocktrans'
--+
 Reporter:  ahagenbruch   |Owner:  pigletto
 Type:  Bug   |   Status:  assigned
Component:  Internationalization  |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by pigletto):

 * cc: pigletto (added)


-- 
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-updates@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] #17375: 'makemessages' ignores plural from 'blocktrans'

[Django]

#17375: 'makemessages' ignores plural from 'blocktrans'
--+
 Reporter:  ahagenbruch   |Owner:  pigletto
 Type:  Bug   |   Status:  assigned
Component:  Internationalization  |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by pigletto):

 Ok, right, it fails for blocktrans that doesn't use 'context'. Uploaded
 patch solves issue as suggested by using xgettext call with multiple files
 at once.

 One thing to modify there yet is to make use of -f, --files-from in cmd
 for xgettext, instead of passing great amount of parameters.

-- 
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-updates@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] #16653: Document kwargs support for urlresolvers.resolve

[Django]

#16653: Document kwargs support for urlresolvers.resolve
-+-
 Reporter:  jedie|Owner:
 Type:   |  krzysiumed
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by jezdez):

 * 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-updates@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] #17390: Describe how to do auth for Class Based Views in the main Auth docs

[Django]

#17390: Describe how to do auth for Class Based Views in the main Auth docs
--+
 Reporter:  ncoghlan@…|Owner:  zsiciarz
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.3
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by zsiciarz):

 * owner:  nobody => zsiciarz


-- 
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-updates@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] #17451: 1.4 release notes should mention new Javascript parsing for makemessages

[Django]

#17451: 1.4 release notes should mention new Javascript parsing for makemessages
-+-
 Reporter:  nedbatchelder|Owner:  zsiciarz
 Type:  Uncategorized|   Status:  new
Component:  Documentation|  Version:
 Severity:  Normal   |  1.4-alpha-1
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by gnosek):

 * 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-updates@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] #13839: select_related caches None for non-existent objects in reverse one-to-one relations

[Django]

#13839: select_related caches None for non-existent objects in reverse 
one-to-one
relations
-+-
 Reporter:  shauncutts   |Owner:  lrekucki
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.2
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by lrekucki):

 * needs_better_patch:  1 => 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-updates@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] #11670: Model fields named 'year', 'month', 'gt', 'lt' etc. get mistaken for lookup types in lookups across relations

[Django]

#11670: Model fields named 'year', 'month', 'gt', 'lt' etc. get mistaken for 
lookup
types in lookups across relations
-+-
 Reporter:  andy@…   |Owner:
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  SVN
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by akaariai):

 * needs_better_patch:  1 => 0


Comment:

 If the patch is good to go, it would be nice to get this into 1.4.

 In that case opening a new ticket about the larger refactor would be nice,
 so that the patches about the refactoring do not get lost.

 I unchecked the "patch needs improvement" box, as I think that is per the
 triaging guide: patch author removes that box when he feels he has
 something ready, reviewer rechecks it, or marks as ready for checkin as
 needed. Unfortunately, I don't have time for review just now.

-- 
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-updates@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] #17375: 'makemessages' ignores plural from 'blocktrans'

[Django]

#17375: 'makemessages' ignores plural from 'blocktrans'
--+
 Reporter:  ahagenbruch   |Owner:  pigletto
 Type:  Bug   |   Status:  assigned
Component:  Internationalization  |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by claudep):

 The only reason it is working in your patch is that the msgid of the
 problematic string in test.html has a msgctxt line.

-- 
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-updates@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] #17451: 1.4 release notes should mention new Javascript parsing for makemessages

[Django]

#17451: 1.4 release notes should mention new Javascript parsing for makemessages
---+---
 Reporter:  nedbatchelder  |Owner:  zsiciarz
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.4-alpha-1
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+---
Changes (by zsiciarz):

 * 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-updates@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] #17541: Unexpected ForeignKey Behavior with self.pk == None

[Django]

#17541: Unexpected ForeignKey Behavior with self.pk == None
-+-
 Reporter:  sheats   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:   |  decision needed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by akaariai):

 * stage:  Ready for checkin => Design decision needed


Comment:

 I don't think this is ready for checkin, as there is still the question of
 how to make this consistent across all the different related object
 descriptors.

 My opinion is that the code should return or qs.none() in the null field
 case. It is a nice feature that if you fetch objects from the DB, and then
 fetch related objects to those objects, you will never get `ValueError`.
 There is a use-case here: you can have nullable unique field which is then
 referenced by some other model - in that case there can be no objects
 related to the instance, but throwing `ValueError` isn't a nice API
 either. Granted, this use case isn't that common, but we can make it work
 for free.

 So, Im marking this as DDN.

-- 
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-updates@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] #17643: Misleading deprecation warnings raised by the cache_page decorator

[Django]

#17643: Misleading deprecation warnings raised by the cache_page decorator
-+-
 Reporter:  zsiciarz |Owner:  zsiciarz
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Core (Other) |  1.4-alpha-1
 Severity:  Normal   |   Resolution:
 Keywords:  deprecation  | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by jezdez):

 * stage:  Unreviewed => 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-updates@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] #17165: SelectDateWidget does not work correctly with has_changed()

[Django]

#17165: SelectDateWidget does not work correctly with has_changed()
-+-
 Reporter:  rene@…   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  SVN
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  SelectDateWidget | Triage Stage:  Accepted
  changed has_changed changed_data   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by jezdez):

 * status:  reopened => closed
 * resolution:   => duplicate


-- 
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-updates@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] #17451: 1.4 release notes should mention new Javascript parsing for makemessages

[Django]

#17451: 1.4 release notes should mention new Javascript parsing for makemessages
---+---
 Reporter:  nedbatchelder  |Owner:  zsiciarz
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.4-alpha-1
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+---
Changes (by zsiciarz):

 * owner:  nobody => zsiciarz


-- 
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-updates@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] #16958: change_password admin view ignores ModelAdmin queryset(request) method

[Django]

#16958: change_password admin view ignores ModelAdmin queryset(request) method
-+-
 Reporter:  mpaolini |Owner:  viciu
 Type:  Bug  |   Status:  assigned
Component:  contrib.auth |  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:  admin, auth  | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by jezdez):

 * 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-updates@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] #16964: FileField files can't be opened in write mode if not closed before

[Django]

#16964: FileField files can't be opened in write mode if not closed before
--+
 Reporter:  jonash|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  File uploads/storage  |  Version:  1.3
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by jezdez):

 * needs_tests:  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-updates@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] #12583: Postgresql backend uses implicit text casts for case insensitive operators

[Django]

#12583: Postgresql backend uses implicit text casts for case insensitive 
operators
-+-
 Reporter:  Ubercore |Owner:  Ubercore
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  SVN
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  postgresql cast  |  Needs documentation:  0
  case-insensitive   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by kwadrat):

 * status:  assigned => closed
 * cc: kwadrat (added)
 * ui_ux:   => 0
 * resolution:   => fixed
 * easy:   => 0


Comment:

 This ticket can be closed because it is already implemented in:
 django/db/backends/postgresql_psycopg2/operations.py, class
 DatabaseOperations, method lookup_cast

-- 
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-updates@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] #17551: Namespaces declared in different places

[Django]

#17551: Namespaces declared in different places
---+--
 Reporter:  Kronuz |Owner:  gnosek
 Type:  Uncategorized  |   Status:  assigned
Component:  Core (URLs)|  Version:  1.3
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by gnosek):

 * needs_better_patch:  1 => 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-updates@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] r17447 - in django/trunk/django: contrib/contenttypes contrib/gis contrib/gis/sitemaps views

[noreply]

Author: jezdez
Date: 2012-02-04 13:01:11 -0800 (Sat, 04 Feb 2012)
New Revision: 17447

Modified:
   django/trunk/django/contrib/contenttypes/views.py
   django/trunk/django/contrib/gis/sitemaps/views.py
   django/trunk/django/contrib/gis/views.py
   django/trunk/django/views/static.py
Log:
Fixed #17458 -- Marked Http404 error messages for translation. Thanks, Claude 
Paroz.

Modified: django/trunk/django/contrib/contenttypes/views.py
===
--- django/trunk/django/contrib/contenttypes/views.py   2012-02-04 20:02:46 UTC 
(rev 17446)
+++ django/trunk/django/contrib/contenttypes/views.py   2012-02-04 21:01:11 UTC 
(rev 17447)
@@ -2,6 +2,7 @@
 from django.contrib.contenttypes.models import ContentType
 from django.contrib.sites.models import Site, get_current_site
 from django.core.exceptions import ObjectDoesNotExist
+from django.utils.translation import ugettext as _
 
 def shortcut(request, content_type_id, object_id):
 """
@@ -11,17 +12,18 @@
 try:
 content_type = ContentType.objects.get(pk=content_type_id)
 if not content_type.model_class():
-raise http.Http404("Content type %s object has no associated model"
-   % content_type_id)
+raise http.Http404(_(u"Content type %(ct_id)s object has no 
associated model") %
+   {'ct_id': content_type_id})
 obj = content_type.get_object_for_this_type(pk=object_id)
 except (ObjectDoesNotExist, ValueError):
-raise http.Http404("Content type %s object %s doesn't exist"
-   % (content_type_id, object_id))
+raise http.Http404(_(u"Content type %(ct_id)s object %(obj_id)s 
doesn't exist") %
+   {'ct_id': content_type_id, 'obj_id': object_id})
+
 try:
 get_absolute_url = obj.get_absolute_url
 except AttributeError:
-raise http.Http404("%s objects don't have a get_absolute_url() method"
-   % content_type.name)
+raise http.Http404(_("%(ct_name)s objects don't have a 
get_absolute_url() method") %
+   {'ct_name': content_type.name})
 absurl = get_absolute_url()
 
 # Try to figure out the object's domain, so we can do a cross-site redirect

Modified: django/trunk/django/contrib/gis/sitemaps/views.py
===
--- django/trunk/django/contrib/gis/sitemaps/views.py   2012-02-04 20:02:46 UTC 
(rev 17446)
+++ django/trunk/django/contrib/gis/sitemaps/views.py   2012-02-04 21:01:11 UTC 
(rev 17447)
@@ -7,6 +7,7 @@
 from django.db import connections, DEFAULT_DB_ALIAS
 from django.db.models import get_model
 from django.utils.encoding import smart_str
+from django.utils.translation import ugettext as _
 
 from django.contrib.gis.shortcuts import render_to_kml, render_to_kmz
 
@@ -40,7 +41,7 @@
 maps, urls = [], []
 if section is not None:
 if section not in sitemaps:
-raise Http404("No sitemap available for section: %r" % section)
+raise Http404(_(u"No sitemap available for section: %r") % section)
 maps.append(sitemaps[section])
 else:
 maps = sitemaps.values()
@@ -54,9 +55,9 @@
 else:
 urls.extend(site.get_urls(page=page, site=current_site))
 except EmptyPage:
-raise Http404("Page %s empty" % page)
+raise Http404(_(u"Page %s empty") % page)
 except PageNotAnInteger:
-raise Http404("No page '%s'" % page)
+raise Http404(_(u"No page '%s'") % page)
 xml = smart_str(loader.render_to_string('gis/sitemaps/geo_sitemap.xml', 
{'urlset': urls}))
 return HttpResponse(xml, content_type='application/xml')
 

Modified: django/trunk/django/contrib/gis/views.py
===
--- django/trunk/django/contrib/gis/views.py2012-02-04 20:02:46 UTC (rev 
17446)
+++ django/trunk/django/contrib/gis/views.py2012-02-04 21:01:11 UTC (rev 
17447)
@@ -1,9 +1,10 @@
 from django.http import Http404
+from django.utils.translation import ugettext as _
 
 def feed(request, url, feed_dict=None):
 """Provided for backwards compatibility."""
 if not feed_dict:
-raise Http404("No feeds are registered.")
+raise Http404(_(u"No feeds are registered."))
 
 try:
 slug, param = url.split('/', 1)
@@ -13,7 +14,7 @@
 try:
 f = feed_dict[slug]
 except KeyError:
-raise Http404("Slug %r isn't registered." % slug)
+raise Http404(_(u"Slug %r isn't registered.") % slug)
 
 instance = f()
 instance.feed_url = getattr(f, 'feed_url', None) or request.path

Modified: django/trunk/django/views/static.py
===
--- django/trunk/django/views/static.py 2012-02-04 20:02:46 UTC (rev 17446)
+++ django/trunk/django/vi

Re: [Django] #17458: Http404 untranslatable strings

[Django]

#17458: Http404 untranslatable strings
--+
 Reporter:  claudep   |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Internationalization  |  Version:  SVN
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by jezdez):

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


Comment:

 In [17447]:
 {{{
 #!CommitTicketReference repository="" revision="17447"
 Fixed #17458 -- Marked Http404 error messages for translation. Thanks,
 Claude Paroz.
 }}}

-- 
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-updates@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] #17139: In the French localflavor, department names are written without accents

[Django]

#17139: In the French localflavor, department names are written without accents
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  SVN
Component:  contrib.localflavor  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by jezdez):

 * 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-updates@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] #159: Circular logout problem

[Django]

#159: Circular logout problem
-+-
 Reporter:  Manuzhai |Owner:
 Type:  Bug  |  ashchristopher
Component:  contrib.admin|   Status:  assigned
 Severity:  Normal   |  Version:
 Keywords:  admin logout |   Resolution:
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by oinopion):

 * stage:  Accepted => Ready for checkin


Comment:

 Patch looks good: has working tests and does what it says on the tin.

-- 
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-updates@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] #17138: Admin sets the "summary" attribute on table, which is obsolete

[Django]

#17138: Admin sets the "summary" attribute on table, which is obsolete
-+-
 Reporter:  aaugustin|Owner:  teraom
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  SVN
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by jezdez):

 * 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-updates@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] #17219: Add a more precise description to some db fields.

[Django]

#17219: Add a more precise description to some db fields.
-+-
 Reporter:  charettes|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Translations |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by jezdez):

 * 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-updates@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] #17236: Documentation of session behavior during login

[Django]

#17236: Documentation of session behavior during login
-+-
 Reporter:  bruth|Owner:
 Type:   |  krzysiumed
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by jezdez):

 * 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-updates@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] #17239: mark_safe(media) in django admin Opzioni

[Django]

#17239: mark_safe(media) in django admin Opzioni
-+-
 Reporter:  riccardodivirgilio   |Owner:  pbnan
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  SVN
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  mark_safe media  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by jezdez):

 * 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-updates@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] #17316: settings.APPEND_SLASH (CommonMiddleware) does not work well behind multiple proxies

[Django]

#17316: settings.APPEND_SLASH (CommonMiddleware) does not work well behind 
multiple
proxies
-+-
 Reporter:  dnozay   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.3
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by jezdez):

 * 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-updates@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] #17319: Internationalization documentation

[Django]

#17319: Internationalization documentation
-+-
 Reporter:  dolma33@…|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.3
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
  internationalization   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by jezdez):

 * 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-updates@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] #17192: next_day from views.generic.dates.DayArchiveView returns None instead of today

[Django]

#17192: next_day from views.generic.dates.DayArchiveView returns None instead of
today
---+
 Reporter:  justin@…   |Owner:  pbnan
 Type:  Bug|   Status:  new
Component:  Generic views  |  Version:  1.3
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by pbnan):

 * owner:  nobody => pbnan


-- 
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-updates@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] #16958: change_password admin view ignores ModelAdmin queryset(request) method

[Django]

#16958: change_password admin view ignores ModelAdmin queryset(request) method
--+
 Reporter:  mpaolini  |Owner:  viciu
 Type:  Bug   |   Status:  assigned
Component:  contrib.auth  |  Version:  1.3
 Severity:  Normal|   Resolution:
 Keywords:  admin, auth   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by viciu):

 * owner:  nobody => viciu
 * 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-updates@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] #17327: contrib.auth management commands ignores --database option

[Django]

#17327: contrib.auth management commands ignores --database option
-+-
 Reporter:  skam |Owner:
|  brianriley
 Type:  New feature  |   Status:  assigned
Component:  contrib.auth |  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:  django db models | Triage Stage:  Ready for
  createsuperuser management |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by jezdez):

 * 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-updates@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] #17358: Switch to arg-style logging instead of string interpolation

[Django]

#17358: Switch to arg-style logging instead of string interpolation
-+-
 Reporter:  spulec   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.3
Component:  Core (Other) |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  logging  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by jezdez):

 * 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-updates@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] #17165: SelectDateWidget does not work correctly with has_changed()

[Django]

#17165: SelectDateWidget does not work correctly with has_changed()
-+-
 Reporter:  rene@…   |Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Forms|  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:  SelectDateWidget | Triage Stage:  Accepted
  changed has_changed changed_data   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by anonymous):

 This is a duplicate of: #17542 that is already fixed

-- 
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-updates@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] #10944: Site app should be able to make absolute URLs.

[Django]

#10944: Site app should be able to make absolute URLs.
---+
 Reporter:  jdunck |Owner:
 Type:  New feature|   Status:  new
Component:  contrib.sites  |  Version:  1.0
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by oinopion):

 site_url tag is a bit useless, as it take path as string. IMHO it should
 work like the url tag taking names and parameters.

-- 
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-updates@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] #17515: custom templates in FilterSpec

[Django]

#17515: custom templates in FilterSpec
-+-
 Reporter:  saxix|Owner:  saxix
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by jezdez):

 * 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-updates@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] #17627: contrib.admin.util is misnamed

[Django]

#17627: contrib.admin.util is misnamed
--+
 Reporter:  PaulM |Owner:  viciu
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  contrib.admin |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by viciu):

 * owner:  nobody => viciu
 * 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-updates@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] #17217: Set nbsp instead of space as thousand separator

[Django]

#17217: Set nbsp instead of space as thousand separator
-+-
 Reporter:  fadeyev  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Translations |  Version:
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by jezdez):

 * 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-updates@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] #17641: HTMLParser has no interesting_cdata attribute with a Python version > 2.7.2 (was: HTMLParser has no interesting_cdata attribute with a Python version > 2.7.1)

[Django]

#17641: HTMLParser has no interesting_cdata attribute with a Python version > 
2.7.2
---+
 Reporter:  ramiro |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  SVN
 Severity:  Release blocker|   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  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-updates@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] #17641: HTMLParser has no interesting_cdata attribute with a Python version > 2.7.1

[Django]

#17641: HTMLParser has no interesting_cdata attribute with a Python version > 
2.7.1
---+
 Reporter:  ramiro |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  SVN
 Severity:  Release blocker|   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by ramiro):

 Ah I'm running the test on Debian unstable, and now I understand why it
 reports `2.7.2.+` as its version. Most surely it includes fixes post 2.7.2

 {{{
 $ python -c 'import sys ; print("Python version: %s" % sys.version)'
 Python version: 2.7.2+ (default, Jan 20 2012, 23:05:38)
 [GCC 4.6.2]
 }}}

-- 
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-updates@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] #17541: Unexpected ForeignKey Behavior with self.pk == None

[Django]

#17541: Unexpected ForeignKey Behavior with self.pk == None
-+-
 Reporter:  sheats   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by oinopion):

 * stage:  Accepted => Ready for checkin


Comment:

 I've check the code. Looks good. Fixes the problem.

-- 
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-updates@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] #17239: mark_safe(media) in django admin Opzioni

[Django]

#17239: mark_safe(media) in django admin Opzioni
--+
 Reporter:  riccardodivirgilio|Owner:  pbnan
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:  mark_safe media   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by pbnan):

 * has_patch:  0 => 1


Comment:

 The change is harmless, as `django.forms.widgets.Media` is being
 "marked_safe" upon rendering in template.

-- 
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-updates@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] #17166: The fixture documentation tells nowhere that you can (should?) use FIXTURE_DIRS in your settings.py

[Django]

#17166: The fixture documentation tells nowhere that you can (should?) use
FIXTURE_DIRS in your settings.py
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.3
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by jezdez):

 * 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-updates@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] #17607: Installing PostGIS on OSX is easy with homebrew

[Django]

#17607: Installing PostGIS on OSX is easy with homebrew
-+-
 Reporter:  estebistec   |Owner:
 Type:  New feature  |  estebistec
Component:  Documentation|   Status:  new
 Severity:  Normal   |  Version:  1.3
 Keywords:  geodjango|   Resolution:
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  1|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by jezdez):

 * 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-updates@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] #17493: Widget.id_for_label() should be an instance method

[Django]

#17493: Widget.id_for_label() should be an instance method
-+-
 Reporter:  julien   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.3
Component:  Forms|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by jezdez):

 * 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-updates@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.