date:20110123

Re: [Django] #14938: "Save as" does not save entries added with a Inline

2011-01-23 Thread Django

#14938: "Save as" does not save entries added with a Inline
---+
  Reporter:  rax   | Owner:  nobody  
Status:  new   | Milestone:  1.3 
 Component:  Forms |   Version:  1.2-beta
Resolution:|  Keywords:  save-as 
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  1   
Needs_better_patch:  1 |  
---+
Changes (by russellm):

  * keywords:  save-as, blocker, regression => save-as

Comment:

 Not sure why I marked this blocker, regression; on inspection, it doesn't
 appear to be either. It's been a problem since at least 1.1.X, and it
 doesn't involve data loss (there's lost data on entry, but nothing
 destructive happens to existing data)

-- 
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] r15287 - in django/branches/releases/1.2.X: django/contrib/admin/templatetags tests/regressiontests/admin_changelist

2011-01-23 Thread noreply

Author: russellm
Date: 2011-01-24 01:10:18 -0600 (Mon, 24 Jan 2011)
New Revision: 15287

Modified:
   
django/branches/releases/1.2.X/django/contrib/admin/templatetags/admin_list.py
   
django/branches/releases/1.2.X/tests/regressiontests/admin_changelist/models.py
   
django/branches/releases/1.2.X/tests/regressiontests/admin_changelist/tests.py
Log:
[1.2.X] Fixed #14982 -- Ensure that EMPTY_CHANGELIST_VALUE is honored for 
nullable foreign keys. Thanks to marcob for the report and fix, and to sontek 
for the test case.

Backport of r15286 from trunk.

Modified: 
django/branches/releases/1.2.X/django/contrib/admin/templatetags/admin_list.py
===
--- 
django/branches/releases/1.2.X/django/contrib/admin/templatetags/admin_list.py  
2011-01-24 07:01:00 UTC (rev 15286)
+++ 
django/branches/releases/1.2.X/django/contrib/admin/templatetags/admin_list.py  
2011-01-24 07:10:18 UTC (rev 15287)
@@ -157,7 +157,11 @@
 if value is None:
 result_repr = EMPTY_CHANGELIST_VALUE
 if isinstance(f.rel, models.ManyToOneRel):
-result_repr = escape(getattr(result, f.name))
+field_val = getattr(result, f.name)
+if field_val is None:
+result_repr = EMPTY_CHANGELIST_VALUE
+else:
+result_repr = escape(field_val)
 else:
 result_repr = display_for_field(value, f)
 if isinstance(f, models.DateField) or isinstance(f, 
models.TimeField):

Modified: 
django/branches/releases/1.2.X/tests/regressiontests/admin_changelist/models.py
===
--- 
django/branches/releases/1.2.X/tests/regressiontests/admin_changelist/models.py 
2011-01-24 07:01:00 UTC (rev 15286)
+++ 
django/branches/releases/1.2.X/tests/regressiontests/admin_changelist/models.py 
2011-01-24 07:10:18 UTC (rev 15287)
@@ -5,5 +5,5 @@
 name = models.CharField(max_length=128)
 
 class Child(models.Model):
-parent = models.ForeignKey(Parent, editable=False)
-name = models.CharField(max_length=30, blank=True)
\ No newline at end of file
+parent = models.ForeignKey(Parent, editable=False, null=True)
+name = models.CharField(max_length=30, blank=True)

Modified: 
django/branches/releases/1.2.X/tests/regressiontests/admin_changelist/tests.py
===
--- 
django/branches/releases/1.2.X/tests/regressiontests/admin_changelist/tests.py  
2011-01-24 07:01:00 UTC (rev 15286)
+++ 
django/branches/releases/1.2.X/tests/regressiontests/admin_changelist/tests.py  
2011-01-24 07:10:18 UTC (rev 15287)
@@ -17,6 +17,26 @@
 m.list_select_related, m.list_per_page, m.list_editable, m)
 self.assertEqual(cl.query_set.query.select_related, {'parent': 
{'name': {}}})
 
+def test_result_list_empty_changelist_value(self):
+"""
+Regression test for #14982: EMPTY_CHANGELIST_VALUE should be honored
+for relationship fields
+"""
+new_child = Child.objects.create(name='name', parent=None)
+request = MockRequest()
+m = ChildAdmin(Child, admin.site)
+cl = ChangeList(request, Child, m.list_display, m.list_display_links,
+m.list_filter, m.date_hierarchy, m.search_fields,
+m.list_select_related, m.list_per_page, m.list_editable, m)
+cl.formset = None
+template = Template('{% load admin_list %}{% spaceless %}{% 
result_list cl %}{% endspaceless %}')
+context = Context({'cl': cl})
+table_output = template.render(context)
+row_html = 'name(None)'
+self.assertFalse(table_output.find(row_html) == -1,
+'Failed to find expected row element: %s' % table_output)
+
+
 def test_result_list_html(self):
 """
 Verifies that inclusion tag result_list generates a table when with

-- 
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] r15286 - in django/trunk: django/contrib/admin/templatetags tests/regressiontests/admin_changelist

2011-01-23 Thread noreply

Author: russellm
Date: 2011-01-24 01:01:00 -0600 (Mon, 24 Jan 2011)
New Revision: 15286

Modified:
   django/trunk/django/contrib/admin/templatetags/admin_list.py
   django/trunk/tests/regressiontests/admin_changelist/models.py
   django/trunk/tests/regressiontests/admin_changelist/tests.py
Log:
Fixed #14982 -- Ensure that EMPTY_CHANGELIST_VALUE is honored for nullable 
foreign keys. Thanks to marcob for the report and fix, and to sontek for the 
test case.

Modified: django/trunk/django/contrib/admin/templatetags/admin_list.py
===
--- django/trunk/django/contrib/admin/templatetags/admin_list.py
2011-01-24 06:36:31 UTC (rev 15285)
+++ django/trunk/django/contrib/admin/templatetags/admin_list.py
2011-01-24 07:01:00 UTC (rev 15286)
@@ -156,7 +156,11 @@
 if value is None:
 result_repr = EMPTY_CHANGELIST_VALUE
 if isinstance(f.rel, models.ManyToOneRel):
-result_repr = escape(getattr(result, f.name))
+field_val = getattr(result, f.name)
+if field_val is None:
+result_repr = EMPTY_CHANGELIST_VALUE
+else:
+result_repr = escape(field_val)
 else:
 result_repr = display_for_field(value, f)
 if isinstance(f, models.DateField) or isinstance(f, 
models.TimeField):

Modified: django/trunk/tests/regressiontests/admin_changelist/models.py
===
--- django/trunk/tests/regressiontests/admin_changelist/models.py   
2011-01-24 06:36:31 UTC (rev 15285)
+++ django/trunk/tests/regressiontests/admin_changelist/models.py   
2011-01-24 07:01:00 UTC (rev 15286)
@@ -5,5 +5,5 @@
 name = models.CharField(max_length=128)
 
 class Child(models.Model):
-parent = models.ForeignKey(Parent, editable=False)
-name = models.CharField(max_length=30, blank=True)
\ No newline at end of file
+parent = models.ForeignKey(Parent, editable=False, null=True)
+name = models.CharField(max_length=30, blank=True)

Modified: django/trunk/tests/regressiontests/admin_changelist/tests.py
===
--- django/trunk/tests/regressiontests/admin_changelist/tests.py
2011-01-24 06:36:31 UTC (rev 15285)
+++ django/trunk/tests/regressiontests/admin_changelist/tests.py
2011-01-24 07:01:00 UTC (rev 15286)
@@ -20,6 +20,26 @@
 m.list_select_related, m.list_per_page, m.list_editable, m)
 self.assertEqual(cl.query_set.query.select_related, {'parent': 
{'name': {}}})
 
+def test_result_list_empty_changelist_value(self):
+"""
+Regression test for #14982: EMPTY_CHANGELIST_VALUE should be honored
+for relationship fields
+"""
+new_child = Child.objects.create(name='name', parent=None)
+request = MockRequest()
+m = ChildAdmin(Child, admin.site)
+cl = ChangeList(request, Child, m.list_display, m.list_display_links,
+m.list_filter, m.date_hierarchy, m.search_fields,
+m.list_select_related, m.list_per_page, m.list_editable, m)
+cl.formset = None
+template = Template('{% load admin_list %}{% spaceless %}{% 
result_list cl %}{% endspaceless %}')
+context = Context({'cl': cl})
+table_output = template.render(context)
+row_html = 'name(None)'
+self.assertFalse(table_output.find(row_html) == -1,
+'Failed to find expected row element: %s' % table_output)
+
+
 def test_result_list_html(self):
 """
 Verifies that inclusion tag result_list generates a table when with

-- 
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] r15285 - in django/trunk: . django/core/cache django/middleware tests/regressiontests/cache

2011-01-23 Thread noreply

Author: russellm
Date: 2011-01-24 00:36:31 -0600 (Mon, 24 Jan 2011)
New Revision: 15285

Modified:
   django/trunk/AUTHORS
   django/trunk/django/core/cache/__init__.py
   django/trunk/django/middleware/cache.py
   django/trunk/tests/regressiontests/cache/tests.py
Log:
Fixed #15144 -- Corrected some problems with the Cache middleware when used 
with multiple cache settings. Thanks to Jim Dalton for the report, and to Jim 
and Joshua Ginsberg for the work on the patch.

Modified: django/trunk/AUTHORS
===
--- django/trunk/AUTHORS2011-01-22 23:29:11 UTC (rev 15284)
+++ django/trunk/AUTHORS2011-01-24 06:36:31 UTC (rev 15285)
@@ -129,6 +129,7 @@
 Jure Cuhalev 
 John D'Agostino 
 dackze+dja...@gmail.com
+Jim Dalton 
 Mihai Damian 
 David Danier 
 Dirk Datzert 

Modified: django/trunk/django/core/cache/__init__.py
===
--- django/trunk/django/core/cache/__init__.py  2011-01-22 23:29:11 UTC (rev 
15284)
+++ django/trunk/django/core/cache/__init__.py  2011-01-24 06:36:31 UTC (rev 
15285)
@@ -110,6 +110,7 @@
 conf = settings.CACHES.get(backend, None)
 if conf is not None:
 args = conf.copy()
+args.update(kwargs)
 backend = args.pop('BACKEND')
 location = args.pop('LOCATION', '')
 return backend, location, args

Modified: django/trunk/django/middleware/cache.py
===
--- django/trunk/django/middleware/cache.py 2011-01-22 23:29:11 UTC (rev 
15284)
+++ django/trunk/django/middleware/cache.py 2011-01-24 06:36:31 UTC (rev 
15285)
@@ -65,7 +65,8 @@
 self.cache_timeout = settings.CACHE_MIDDLEWARE_SECONDS
 self.key_prefix = settings.CACHE_MIDDLEWARE_KEY_PREFIX
 self.cache_anonymous_only = getattr(settings, 
'CACHE_MIDDLEWARE_ANONYMOUS_ONLY', False)
-self.cache = get_cache(settings.CACHE_MIDDLEWARE_ALIAS)
+self.cache_alias = settings.CACHE_MIDDLEWARE_ALIAS
+self.cache = get_cache(self.cache_alias)
 
 def process_response(self, request, response):
 """Sets the cache, if needed."""
@@ -101,7 +102,8 @@
 self.cache_timeout = settings.CACHE_MIDDLEWARE_SECONDS
 self.key_prefix = settings.CACHE_MIDDLEWARE_KEY_PREFIX
 self.cache_anonymous_only = getattr(settings, 
'CACHE_MIDDLEWARE_ANONYMOUS_ONLY', False)
-self.cache = get_cache(settings.CACHE_MIDDLEWARE_ALIAS)
+self.cache_alias = settings.CACHE_MIDDLEWARE_ALIAS
+self.cache = get_cache(self.cache_alias)
 
 def process_request(self, request):
 """
@@ -152,8 +154,9 @@
 # we need to use middleware defaults.
 
 cache_kwargs = {}
+
 try:
-self.key_prefix = kwargs.get('key_prefix')
+self.key_prefix = kwargs['key_prefix']
 if self.key_prefix is not None:
 cache_kwargs['KEY_PREFIX'] = self.key_prefix
 else:
@@ -161,14 +164,15 @@
 except KeyError:
 self.key_prefix = settings.CACHE_MIDDLEWARE_KEY_PREFIX
 cache_kwargs['KEY_PREFIX'] = self.key_prefix
+
 try:
-cache_alias = kwargs.get('cache_alias')
-if cache_alias is None:
-cache_alias = DEFAULT_CACHE_ALIAS
+self.cache_alias = kwargs['cache_alias']
+if self.cache_alias is None:
+self.cache_alias = DEFAULT_CACHE_ALIAS
 if cache_timeout is not None:
 cache_kwargs['TIMEOUT'] = cache_timeout
 except KeyError:
-cache_alias = settings.CACHE_MIDDLEWARE_ALIAS
+self.cache_alias = settings.CACHE_MIDDLEWARE_ALIAS
 if cache_timeout is None:
 cache_kwargs['TIMEOUT'] = settings.CACHE_MIDDLEWARE_SECONDS
 else:
@@ -179,5 +183,5 @@
 else:
 self.cache_anonymous_only = cache_anonymous_only
 
-self.cache = get_cache(cache_alias, **cache_kwargs)
+self.cache = get_cache(self.cache_alias, **cache_kwargs)
 self.cache_timeout = self.cache.default_timeout

Modified: django/trunk/tests/regressiontests/cache/tests.py
===
--- django/trunk/tests/regressiontests/cache/tests.py   2011-01-22 23:29:11 UTC 
(rev 15284)
+++ django/trunk/tests/regressiontests/cache/tests.py   2011-01-24 06:36:31 UTC 
(rev 15285)
@@ -1133,10 +1133,14 @@
 def setUp(self):
 self.orig_cache_middleware_alias = settings.CACHE_MIDDLEWARE_ALIAS
 self.orig_cache_middleware_key_prefix = 
settings.CACHE_MIDDLEWARE_KEY_PREFIX
+self.orig_cache_middleware_seconds = settings.CACHE_MIDDLEWARE_SECONDS
+

Re: [Django] #15144: Max age set in cache control no longer obeys timeout set with @cache_page decorator

2011-01-23 Thread Django

#15144: Max age set in cache control no longer obeys timeout set with 
@cache_page
decorator
+---
  Reporter:  jsdalton   | Owner:  nobody 
Status:  new| Milestone:  1.3
 Component:  Cache system   |   Version:  SVN
Resolution: |  Keywords:  blocker, regression
 Stage:  Ready for checkin  | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * stage:  Unreviewed => Ready for checkin

Comment:

 Ok - your test case now makes it clear that there are a couple of bugs.
 I'm marking RFC, will check in shortly with a couple of minor
 modifications.

 In particular:

  * Using try:catch logic instead of "if contains" logic is marginally
 faster, because it only requires one lookup for all cases, rather than two
 lookups on the successful lookup case.
  * The or-emulate "ternary if" is prone to error, especially in the "if x
 is None" versus "x is False" case, so we generally prefer the explicit if
 statement.

-- 
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] #15127: form.fields is still tied to class variables

2011-01-23 Thread Django

#15127: form.fields is still tied to class variables
-+--
  Reporter:  absoludity  | Owner:  nobody
Status:  new | Milestone:
 Component:  Forms   |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

  * 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] #15129: Invalid order of applying formats

2011-01-23 Thread Django

#15129: Invalid order of applying formats
---+
  Reporter:  tonnzor   | Owner:  nobody
Status:  new   | Milestone:  1.3   
 Component:  Internationalization  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Changes (by russellm):

  * needs_better_patch:  0 => 1
  * 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] #15130: Model.validate_unique method doesn't take in account multi-db

2011-01-23 Thread Django

#15130: Model.validate_unique method doesn't take in account multi-db
--+-
  Reporter:  t2y  | Owner:  
Status:  reopened | Milestone:  1.3 
 Component:  ORM aggregation  |   Version:  1.2 
Resolution:   |  Keywords:  multi-db
 Stage:  Accepted | Has_patch:  1   
Needs_docs:  0|   Needs_tests:  1   
Needs_better_patch:  0|  
--+-
Changes (by t2y):

  * 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] #15130: Model.validate_unique method doesn't take in account multi-db

2011-01-23 Thread Django

#15130: Model.validate_unique method doesn't take in account multi-db
--+-
  Reporter:  t2y  | Owner:  
Status:  reopened | Milestone:  1.3 
 Component:  ORM aggregation  |   Version:  1.2 
Resolution:   |  Keywords:  multi-db
 Stage:  Accepted | Has_patch:  0   
Needs_docs:  0|   Needs_tests:  1   
Needs_better_patch:  0|  
--+-
Changes (by t2y):

  * status:  closed => reopened
  * has_patch:  1 => 0
  * resolution:  worksforme =>

Comment:

 Hi ramiro, thank you for reviewing and making tests code.
 Though my explanation was not good, this problem occur only when a
 Model.validate_unique method is called. So, I fixed your test code to call
 validate_unique method. By running my test code, you can see
 ValidationError.

 I think what the save method was successed makes you wonder. The reason
 why the save mehtod is considered with "using" parameter for multi-db.

-- 
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] #15117: get_or_create() raises "DatabaseError: no such savepoint" instead of IntegrityError (PostgreSQL)

2011-01-23 Thread Django

#15117: get_or_create() raises "DatabaseError: no such savepoint" instead of
IntegrityError (PostgreSQL)
---+
  Reporter:  akaihola  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 Agreed; a savepoint error isn't the right response here. I'm not
 completely convinced that IntegrityError is right, either; get_or_create
 should be able to... well... get, or create. However, I can see that there
 are issues with that in practice.

-- 
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] #15125: UpdateView should introspect form_class instead of requiring you to pass the model

2011-01-23 Thread Django

#15125: UpdateView should introspect form_class instead of requiring you to pass
the model
+---
  Reporter:  sontek | Owner:  nobody
Status:  new| Milestone:  1.3   
 Component:  Generic views  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  1  |  
+---
Changes (by russellm):

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

Comment:

 Accepted on the basis that yes, model information will be available under
 some circumstances, and shouldn't require double-entry. However, I have
 two problems with the provided patch.

 Firstly, this presumes that form_class has a _meta.model, which it wont
 unless you have a ModelForm. Forms don't have to be model forms in order
 to save a model.

 Secondly, I'd rather see this handled by introducing a get_model() entry
 point, rather than using the constructor. The default implementation would
 just return self.model, but this would provide the flexibility for
 arbitrary control of the source model, including introspection of
 form_class when possible.

-- 
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] #15149: Memcached backend: possible issue with cache keys

2011-01-23 Thread Django

#15149: Memcached backend: possible issue with cache keys
-+--
  Reporter:  j...@jeffcroft.com  | Owner:  nobody   
Status:  new | Milestone:   
 Component:  Cache system|   Version:  SVN  
Resolution:  |  Keywords:  memcached
 Stage:  Unreviewed  | Has_patch:  0
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Comment (by Jeff Croft):

 I've also verified that this problem only applies to the memcached backend
 -- locmem, for example, works fine.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #15111: manage.py test fails if sites app not installed

2011-01-23 Thread Django

#15111: manage.py test fails if sites app not installed
+---
  Reporter:  wkornewald | Owner:  nobody
Status:  new| Milestone:  1.3   
 Component:  Contrib apps   |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 Marking RFC because the patch is pretty much ready to use.

 However, I have a suspicion that the very last delta is wrong (or at least
 requires additional thought). The call to get_current() is intended to
 populate a cache; it shouldn't be possible to remove that line without
 consequences.

-- 
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] #6386: hash() in creating db names is unpredictable, and unnecessary

2011-01-23 Thread Django

#6386: hash() in creating db names is unpredictable, and unnecessary
-+--
  Reporter:  nedbatchelder   | Owner:  elbarto
Status:  closed  | Milestone: 
 Component:  Core framework  |   Version:  SVN
Resolution:  fixed   |  Keywords: 
 Stage:  Accepted| Has_patch:  0  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by elbarto):

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

Comment:

 The ticket is obsolete. It was fixed in r8296 where the database backend
 code was refactored.

-- 
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] #6386: hash() in creating db names is unpredictable, and unnecessary

2011-01-23 Thread Django

#6386: hash() in creating db names is unpredictable, and unnecessary
-+--
  Reporter:  nedbatchelder   | Owner:  elbarto
Status:  new | Milestone: 
 Component:  Core framework  |   Version:  SVN
Resolution:  |  Keywords: 
 Stage:  Accepted| Has_patch:  0  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by elbarto):

  * owner:  nobody => elbarto

-- 
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] #15107: Convert core commands to use self.std(out|err) instead of sys.std(out|err)/print

2011-01-23 Thread Django

#15107: Convert core commands to use self.std(out|err) instead of
sys.std(out|err)/print
--+-
  Reporter:  mmcnickle| Owner:  mmcnickle
Status:  new  | Milestone:  1.3  
 Component:  django-admin.py  |   Version:  SVN  
Resolution:   |  Keywords:   
 Stage:  Accepted | Has_patch:  0
Needs_docs:  0|   Needs_tests:  0
Needs_better_patch:  0|  
--+-
Changes (by russellm):

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

Comment:

 For background -- the transition to self.stdout/stderr was done to ensure
 easy testing, and as a side effect, to allow Django commands to be used as
 a service. We've converted those commands that needed to be converted for
 the purpose of Django's own testing; the remainder is left as a work in
 progress.

-- 
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] #15100: Tests for garbage input templates

2011-01-23 Thread Django

#15100: Tests for garbage input templates
--+-
  Reporter:  steveire | Owner:  nobody
Status:  closed   | Milestone:
 Component:  Template system  |   Version:  1.2   
Resolution:  wontfix  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by russellm):

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

Comment:

 These might be good tests of a new parsing engine, but I'm not sure I see
 why they need to be added to trunk now -- they're not especially rigorous
 tests of the exisiting regex-based parser.

-- 
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] #15101: GeoQuerySet extent() method fails to limit

2011-01-23 Thread Django

#15101: GeoQuerySet extent() method fails to limit
-+--
  Reporter:  billt...@gmail.com  | Owner:  nobody  
Status:  new | Milestone:  
 Component:  GIS |   Version:  1.2 
Resolution:  |  Keywords:  extent()
 Stage:  Accepted| Has_patch:  0   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

  * stage:  Unreviewed => Accepted

Comment:

 Accepting on the basis that jbronn has seen it, and didn't reject it out
 of hand.

-- 
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] #15099: ModelFormset.queryset requirement is too strict

2011-01-23 Thread Django

#15099: ModelFormset.queryset requirement is too strict
---+
  Reporter:  Ciantic   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Forms |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * component:  Uncategorized => Forms
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 On principle, no objection here. Of course, the devil is in the detail --
 especially around the implicit preconditions that querysets satisfy that a
 list may not necessarily satisfy (such as guaranteed ordering).

 This would also be a good exercise in abstraction, separating the "list-
 like" bits of formsets from the queryset-specific bits.

-- 
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] #15098: SiteProfileNotAvailable needs silent_variable_failure=True

2011-01-23 Thread Django

#15098: SiteProfileNotAvailable needs silent_variable_failure=True
-+--
  Reporter:  tkolar  | Owner:  nobody   
  
Status:  new | Milestone:   
  
 Component:  Authentication  |   Version:  SVN  
  
Resolution:  |  Keywords:  SiteProfileNotAvailable 
silent_variable_failure
 Stage:  Accepted| Has_patch:  1
  
Needs_docs:  0   |   Needs_tests:  1
  
Needs_better_patch:  1   |  
-+--
Changes (by russellm):

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

Comment:

 Seems like a reasonable suggestion. I can't think of any reason that
 get_profile should raise an exception during template rendering.

 For future reference, please upload patches, rather than full files.
 Patches should also include tests to validate that the change does what it
 says.

-- 
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] #8890: Inline model formsets break validation for unique_together with foreign keys

2011-01-23 Thread Django

#8890: Inline model formsets break validation for unique_together with foreign
keys
-+--
  Reporter:  mas...@mit.edu  | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Forms   |   Version:  1.0   
Resolution:  invalid |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

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

Comment:

 Closing invalid. This report doesn't contain enough detail to reproduce
 the problem accurately -- it has foreign keys to models that don't exist,
 and a Manager object that isn't provided.

 It doesn't describe the sequence of operations that are required to
 reproduce the problem, either -- it just talks about to 'validation", and
 refers to a "validation step before", but isn't clear about what
 validation step is the problem, or which one comes "before".

 If anyone can provide a clear, reproducible test case, please reopen.

-- 
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] #5423: "dumpdata" should stream output one row at a time

2011-01-23 Thread Django

#5423: "dumpdata" should stream output one row at a time
+---
  Reporter:  adrian | Owner:  ramiro
   
Status:  assigned   | Milestone:
   
 Component:  Serialization  |   Version:  SVN   
   
Resolution: |  Keywords:  dumpdata loaddata 
fixtures memory
 Stage:  Accepted   | Has_patch:  1 
   
Needs_docs:  0  |   Needs_tests:  0 
   
Needs_better_patch:  0  |  
+---
Changes (by ramiro):

  * 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] #7145: 'NoneType' object has no attribute 'year' in admin change list when using date_hierarchy with a date field with null values

2011-01-23 Thread Django

#7145: 'NoneType' object has no attribute 'year' in admin change list when using
date_hierarchy with a date field with null values
--+-
  Reporter:  Eric Walstad   | Owner:  
nobody
Status:  closed   | Milestone:  1.3 
  
 Component:  django.contrib.admin |   Version:  SVN 
  
Resolution:  worksforme   |  Keywords:  
  
 Stage:  Unreviewed   | Has_patch:  1   
  
Needs_docs:  0|   Needs_tests:  0   
  
Needs_better_patch:  0|  
--+-
Changes (by russellm):

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

Comment:

 Works for me; Provided test cases pass for me on trunk and 1.2.X.

-- 
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] #15149: Memcached backend: possible issue with cache keys

2011-01-23 Thread Django

#15149: Memcached backend: possible issue with cache keys
-+--
  Reporter:  j...@jeffcroft.com  | Owner:  nobody   
Status:  new | Milestone:   
 Component:  Cache system|   Version:  SVN  
Resolution:  |  Keywords:  memcached
 Stage:  Unreviewed  | Has_patch:  0
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Comment (by anonymous):

 I've just validated that this problem does NOT happen if I roll back to
 revision 13794 (right before this commit:
 http://code.djangoproject.com/ticket/13795).

 Memcached definitely running. I can telnet to it with no problem. Python
 2.6.2.

 Thanks!

-- 
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] #15149: Memcached backend: possible issue with cache keys

2011-01-23 Thread Django

#15149: Memcached backend: possible issue with cache keys
-+--
  Reporter:  j...@jeffcroft.com  | Owner:  nobody   
Status:  new | Milestone:   
 Component:  Cache system|   Version:  SVN  
Resolution:  |  Keywords:  memcached
 Stage:  Unreviewed  | Has_patch:  0
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by jezdez):

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

Comment:

 Trying to reproduce the problem, this is what I got:

 {{{
 >>> from django.core.cache import cache
 >>> cache.clear()
 >>> cache.get('testing_yo')
 >>> cache.set('testing_yo', 'testing, yo!', 300)
 >>> cache.key_prefix
 'barstar_'
 >>> # Using Django's cache framework's get method
 >>> cache.get('testing_yo')
 'testing, yo!'
 >>> cache.get('%stesting_yo' % cache.key_prefix)
 >>>
 >>> # Using the underlying memcached instance
 >>> cache._cache.get('testing_yo')
 >>> cache._cache.get('%stesting_yo' % cache.key_prefix)
 >>>
 }}}

 I know it sounds awful to ask, but can you validate that the memcache
 server is running? Also what Python and OS?

-- 
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] #15149: Memcached backend: possible issue with cache keys

2011-01-23 Thread Django

#15149: Memcached backend: possible issue with cache keys
+---
 Reporter:  j...@jeffcroft.com  |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Cache system| Version:  SVN   
 Keywords:  memcached   |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 I'm using django trunk, revision 15284. There appears to be some issue
 with the memcache backend, as I'm able to set cache items, but not get
 them. It seems as though the problem may be that items are being set with
 the wrong cache key. Documentation of my issue is in this gist:

 https://gist.github.com/792466

-- 
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] #12988: Add support of IDN domains for URLField validator.

2011-01-23 Thread Django

#12988: Add support of IDN domains for URLField validator.
---+
  Reporter:  niksite   | Owner:  nobody
Status:  new   | Milestone:  1.3   
 Component:  Forms |   Version:  SVN   
Resolution:|  Keywords:  IDN   
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by jezdez):

  * has_patch:  0 => 1
  * milestone:  => 1.3

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #15036: Ukrainian translation (update)

2011-01-23 Thread Django

#15036: Ukrainian translation (update)
+---
  Reporter:  sv0| Owner:  nobody

Status:  closed | Milestone:

 Component:  Translations   |   Version:  1.2   

Resolution:  wontfix|  Keywords:  translation, uk, 
ukrainian
 Stage:  Ready for checkin  | Has_patch:  1 

Needs_docs:  0  |   Needs_tests:  0 

Needs_better_patch:  0  |  
+---
Changes (by claudep):

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

-- 
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] #15036: Ukrainian translation (update)

2011-01-23 Thread Django

#15036: Ukrainian translation (update)
+---
  Reporter:  sv0| Owner:  nobody

Status:  new| Milestone:

 Component:  Translations   |   Version:  1.2   

Resolution: |  Keywords:  translation, uk, 
ukrainian
 Stage:  Ready for checkin  | Has_patch:  1 

Needs_docs:  0  |   Needs_tests:  0 

Needs_better_patch:  0  |  
+---
Comment (by claudep):

 Django translations are now done through the Transifex project.

 You will find all required information on the Django documentation
 website:

 http://docs.djangoproject.com/en/dev/internals/contributing/#submitting-
 and-maintaining-translations

-- 
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] #15027: Updated RU translation

2011-01-23 Thread Django

#15027: Updated RU translation
---+
  Reporter:  blackraven| Owner:  blackraven 
Status:  closed| Milestone: 
 Component:  Translations  |   Version:  SVN
Resolution:  wontfix   |  Keywords:  russian translation
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by claudep):

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

Comment:

 Django translations are now done through the Transifex project.

 You will find all required information on the Django documentation
 website:

 http://docs.djangoproject.com/en/dev/internals/contributing/#submitting-
 and-maintaining-translations

-- 
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] #14934: Decimal errors not localized to LT because of dictionary interpolation

2011-01-23 Thread Django

#14934: Decimal errors not localized to LT because of dictionary interpolation
---+
  Reporter:  davidlmontgomery  | Owner:  nobody
Status:  closed| Milestone:
 Component:  Translations  |   Version:  1.2   
Resolution:  wontfix   |  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by claudep):

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

Comment:

 Django translations are now done through the Transifex project.

 You will find all required information on the Django documentation
 website:

 http://docs.djangoproject.com/en/dev/internals/contributing/#submitting-
 and-maintaining-translations

-- 
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] #14913: Romanian translation, including E date format

2011-01-23 Thread Django

#14913: Romanian translation, including E date format
+---
  Reporter:  mihneasim  | Owner:  nobody   
Status:  closed | Milestone:  1.3  
 Component:  Translations   |   Version:  SVN  
Resolution:  wontfix|  Keywords:  translations romanian
 Stage:  Ready for checkin  | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by claudep):

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

Comment:

 Django translations are now done through the Transifex project.

 You will find all required information on the Django documentation
 website:

 http://docs.djangoproject.com/en/dev/internals/contributing/#submitting-
 and-maintaining-translations

-- 
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] #14309: Spanish translation on deleting objects

2011-01-23 Thread Django

#14309: Spanish translation on deleting objects
---+
  Reporter:  asi...@gmail.com  | Owner:  nobody   
Status:  closed| Milestone:   
 Component:  Translations  |   Version:  1.2  
Resolution:  wontfix   |  Keywords:  Spanish 1.2.x
 Stage:  Accepted  | Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by claudep):

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

Comment:

 Django translations are now done through the Transifex project.

 You will find all required information on the Django documentation
 website:

 http://docs.djangoproject.com/en/dev/internals/contributing/#submitting-
 and-maintaining-translations

-- 
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] #15144: Max age set in cache control no longer obeys timeout set with @cache_page decorator

2011-01-23 Thread Django

#15144: Max age set in cache control no longer obeys timeout set with 
@cache_page
decorator
---+
  Reporter:  jsdalton  | Owner:  nobody 
Status:  new   | Milestone:  1.3
 Component:  Cache system  |   Version:  SVN
Resolution:|  Keywords:  blocker, regression
 Stage:  Unreviewed| Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Comment (by jsdalton):

 Okay, I'm uploading a new patch that:

  * Includes the regression tests I wrote under `test_view_decorator` that
 demonstrating the original issue
  * Fixes the issue originally raised in this ticket by incorporating
 Joshua's patch (15144.patch).
  * Includes a new test under `CacheMiddlewareTest`, `test_constructor`,
 which highlight a few bugs in the constructor that were discussed briefly
 here: http://groups.google.com/group/django-
 developers/browse_thread/thread/1a019e9d30de5c9d
  * Fixes the issues uncovered by the new test via a fairly minor rewrite
 of the `__init__` method of `CacheMiddleware`

 With regards to the first issue and fix, that's pretty much been discussed
 above so no need to say more about it.

 With regards to the second issue and fix, the main problem was that if the
 `CacheMiddleware` class was being used as middleware, the values for some
 of the instance attributes were not being set properly. (Basically, the
 `except KeyError` code path was never being executed.)

 The new test should be pretty self explanatory and should raise several
 failures when run against the original `CacheMiddleware.__init__` code
 currently in trunk

 The rewrite is also hopefully self explanatory as well. In addition to
 fixing the bugs I tried my best to simplify some of the code in an effort
 to make it more readable and easy to maintain going forward. A few notes
 of clarification:

  * I changed `cache_alias` to an instance attribute (i.e.
 `self.cache_alias`) in order to make it more testable (since it's not
 possible to determine which alias is being used from `self.cache` itself.)
  * I smoothed out a lot of places where variables were being explicitly
 compared against None etc. I think the new test adequately ensures that
 the appropriate initialization behavior is taking place, and some of those
 constructions were (IMO) making the code a bit unnecessarily verbose and
 hard to read.
  * I wish there was better testing to ensure the right values are being
 set in `cache_kwargs` and passed to `get_cache()` but I think the other
 upstream tests should fail if any of that were going wrong so it's
 probably okay.

 Anyhow, please let me know if there are any issues with the patch or
 anything else that needs to be addressed. (Apologies if I should have
 opened a new ticket to address those other bugs, I just figured it was
 easier to get it all taken care of here.)

 Cheers.

 Jim

-- 
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] #14553: es_AR language update

2011-01-23 Thread Django

#14553: es_AR language update
---+
  Reporter:  dariog| Owner:  nobody
Status:  closed| Milestone:
 Component:  Translations  |   Version:  1.2   
Resolution:  wontfix   |  Keywords:  es_AR 
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by claudep):

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

Comment:

 Django translations are now done through the Transifex project.

 You will find all required information on the Django documentation
 website:

 http://docs.djangoproject.com/en/dev/internals/contributing/#submitting-
 and-maintaining-translations

-- 
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] #8890: Inline model formsets break validation for unique_together with foreign keys

2011-01-23 Thread Django

#8890: Inline model formsets break validation for unique_together with foreign
keys
-+--
  Reporter:  mas...@mit.edu  | Owner:  nobody
Status:  reopened| Milestone:
 Component:  Forms   |   Version:  1.0   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by bronger):

 Sorry, I meant "The unique_together" constrain of the child model ...

-- 
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] #8890: Inline model formsets break validation for unique_together with foreign keys

2011-01-23 Thread Django

#8890: Inline model formsets break validation for unique_together with foreign
keys
-+--
  Reporter:  mas...@mit.edu  | Owner:  nobody
Status:  reopened| Milestone:
 Component:  Forms   |   Version:  1.0   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by bronger):

 * cc: bron...@physik.rwth-aachen.de (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] #8890: Inline model formsets break validation for unique_together with foreign keys

2011-01-23 Thread Django

#8890: Inline model formsets break validation for unique_together with foreign
keys
-+--
  Reporter:  mas...@mit.edu  | Owner:  nobody
Status:  reopened| Milestone:
 Component:  Forms   |   Version:  1.0   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by bronger):

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

Comment:

 I run into the same problem with SVN 13265.  The unique_constraing of the
 child model is not checked by the form set returned by
 {{{inlineformset_factory}}}.  Instead, the integrity error is raised.  My
 code is equivalent to the code above except that I don't have custom form
 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] #14129: Fix Slovenian translation plural-forms

2011-01-23 Thread Django

#14129: Fix Slovenian translation plural-forms
---+
  Reporter:  gasperzejn| Owner:  nobody
Status:  new   | Milestone:
 Component:  Translations  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by claudep):

  * summary:  Updated Slovenian translation for 1.2.x => Fix Slovenian
  translation plural-forms
  * stage:  Ready for checkin => Accepted

Comment:

 Django translations are now done through the Transifex project.

 You will find all required information on the Django documentation
 website:

 http://docs.djangoproject.com/en/dev/internals/contributing/#submitting-
 and-maintaining-translations

 I'm just letting the bug open for the plural-form change. We need to check
 if it is feasible through Transifex.

-- 
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] #14080: Flatpages pt-br translation

2011-01-23 Thread Django

#14080: Flatpages pt-br translation
---+
  Reporter:  canassa   | Owner:  anonymous
Status:  closed| Milestone:   
 Component:  Translations  |   Version:  1.2  
Resolution:  wontfix   |  Keywords:   
 Stage:  Accepted  | Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by claudep):

  * status:  assigned => closed
  * resolution:  => wontfix

Comment:

 Django translations are now done through the Transifex project.

 You will find all required information on the Django documentation
 website:

 http://docs.djangoproject.com/en/dev/internals/contributing/#submitting-
 and-maintaining-translations

-- 
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] #13833: Fix for Indonesian localization

2011-01-23 Thread Django

#13833: Fix for Indonesian localization
---+
  Reporter:  rodin | Owner:  nobody
Status:  new   | Milestone:
 Component:  Translations  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Comment (by claudep):

 Django translations are now done through the Transifex project.

 You will find all required information on the Django documentation
 website:

 http://docs.djangoproject.com/en/dev/internals/contributing/#submitting-
 and-maintaining-translations

 This ticket remains valid for fixes in the
 django/conf/locale/id/formats.py. Could you please provide a patch for
 this file only?

-- 
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] #13577: New Polish L10N formats file

2011-01-23 Thread Django

#13577: New Polish L10N formats file
---+
  Reporter:  ludwik| Owner:  zgoda
Status:  reopened  | Milestone:   
 Component:  Translations  |   Version:  1.2  
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by claudep):

  * has_patch:  1 => 0

Comment:

 Needs a new patch

-- 
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] #2445: [patch] allow callable values for limit_choices_to

2011-01-23 Thread Django

#2445: [patch] allow callable values for limit_choices_to
+---
  Reporter:  mich...@actrix.gen.nz  | Owner:  nobody
Status:  new| Milestone:
 Component:  Core framework |   Version:
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  1  |   Needs_tests:  1 
Needs_better_patch:  1  |  
+---
Changes (by russamos):

 * cc: russamos (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] #2594: Template system should handle whitespace better

2011-01-23 Thread Django

#2594: Template system should handle whitespace better
--+-
  Reporter:  Gary Wilson   | Owner:  
jshedd
Status:  new  | Milestone:  
  
 Component:  Template system  |   Version:  SVN 
  
Resolution:   |  Keywords:  
  
 Stage:  Accepted | Has_patch:  1   
  
Needs_docs:  0|   Needs_tests:  0   
  
Needs_better_patch:  0|  
--+-
Changes (by steveire):

  * needs_better_patch:  1 => 0
  * needs_docs:  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] #12926: bulgarian translation for v 1.1.1

2011-01-23 Thread Django

#12926: bulgarian translation for v 1.1.1
---+
  Reporter:  anonymous | Owner:  nobody   
Status:  closed| Milestone:   
 Component:  Translations  |   Version:  1.1  
Resolution:  wontfix   |  Keywords:  bulgarian
 Stage:  Accepted  | Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  1 |  
---+
Changes (by claudep):

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

Comment:

 Django translations are now done through the Transifex project.

 You will find all required information on the Django documentation
 website:

 http://docs.djangoproject.com/en/dev/internals/contributing/#submitting-
 and-maintaining-translations

-- 
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] #5423: "dumpdata" should stream output one row at a time

2011-01-23 Thread Django

#5423: "dumpdata" should stream output one row at a time
+---
  Reporter:  adrian | Owner:  ramiro
   
Status:  assigned   | Milestone:
   
 Component:  Serialization  |   Version:  SVN   
   
Resolution: |  Keywords:  dumpdata loaddata 
fixtures memory
 Stage:  Accepted   | Has_patch:  1 
   
Needs_docs:  0  |   Needs_tests:  0 
   
Needs_better_patch:  1  |  
+---
Changes (by ramiro):

  * owner:  nobody => ramiro
  * 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] #15148: International Domain Name (IDN) validation not working 100%

2011-01-23 Thread Django

#15148: International Domain Name (IDN) validation not working 100%
-+--
  Reporter:  halrobertson| Owner:  nobody  
Status:  closed  | Milestone:  
 Component:  Core framework  |   Version:  1.3-beta
Resolution:  duplicate   |  Keywords:  
 Stage:  Unreviewed  | Has_patch:  0   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by lrekucki):

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

Comment:

 Duplicate of #12988.

-- 
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] #15148: International Domain Name (IDN) validation not working 100%

2011-01-23 Thread Django

#15148: International Domain Name (IDN) validation not working 100%
-+--
  Reporter:  halrobertson| Owner:  nobody  
Status:  new | Milestone:  
 Component:  Core framework  |   Version:  1.3-beta
Resolution:  |  Keywords:  
 Stage:  Unreviewed  | Has_patch:  0   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by halrobertson):

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

Comment:

 I should mention the results I get:

 # http://www.yahoo.com OK
 # http://yahoo.com OK
 # http://sãopaulo.com/ OK
 # http://sãopaulo.com.br/ OK
 # http://пример.испытание/ FAILED VALIDATION
 # http://مثال.إختبار/ FAILED VALIDATION
 # http://例子.测试/ FAILED VALIDATION
 # http://例子.測試/ FAILED VALIDATION
 # http://उदाहरण.परीक्षा/ FAILED VALIDATION
 # http://例え.テスト/ FAILED VALIDATION
 # http://مثال.آزمایشی/ FAILED VALIDATION
 # http://실례.테스트/ FAILED VALIDATION
 # http://العربية.idn.icann.org/ 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.

[Django] #15148: International Domain Name (IDN) validation not working 100%

2011-01-23 Thread Django

#15148: International Domain Name (IDN) validation not working 100%
+---
 Reporter:  halrobertson|   Owner:  nobody
   Status:  new |   Milestone:
Component:  Core framework  | Version:  1.3-beta  
 Keywords:  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 I am finding some domain names that are valid IDN's not validating with
 Django's URLValidator.  I am using django 1.3.0 beta 1

 I made a simple view to validate some IDN's, including those listed here:
 rooftopsolutions.nl/blog/internationalized-domain-names-are-you-ready

 I have tried this with both python 2.5 and python 2.6 and have the same
 problems in both

 Here's the view code I tried (attached)

-- 
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.

49 matches

Mail list logo