date:20090317

[Django] #10532: An overridden get method on a custom manager passed to get_object_or_404 will not be called.

2009-03-17 Thread Django

#10532: An overridden get method on a custom manager passed to get_object_or_404
will not be called.
---+
 Reporter:  anonymous  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 If a manager is passed in as the first argument to get_object_or_404,
 _get_queryset will convert it into a queryset via manager.all().
 This means that an overridden get method on the manager passed to
 get_object_or_404 will not be called.  This is rather unintuitive.

 {{{
 # In django.shortcuts __init__.py
 def _get_queryset(klass):
 """
 Returns a QuerySet from a Model, Manager, or QuerySet. Created to make
 get_object_or_404 and get_list_or_404 more DRY.
 """
 if isinstance(klass, QuerySet):
 return klass
 elif isinstance(klass, Manager):
 manager = klass
 else:
 manager = klass._default_manager
 return manager.all()


 def get_object_or_404(klass, *args, **kwargs):
 #...
 queryset = _get_queryset(klass)
 try:
 return queryset.get(*args, **kwargs)
 #...
 }}}

 Perhaps it should just be return manager instead of manager.all().

-- 
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] #2131: [patch] HttpResponseSendFile for serving static files handler-specific sendfile mechanism

2009-03-17 Thread Django

#2131: [patch] HttpResponseSendFile for serving static files handler-specific
sendfile mechanism
---+
  Reporter:  ymasuda[at]ethercube.com  | Owner:  alsleme 
Status:  new   | Milestone:  1.1 beta
 Component:  Core framework|   Version:  SVN 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  1 |   Needs_tests:  1   
Needs_better_patch:  1 |  
---+
Comment (by jacob):

 That should be pretty easy to pull off, I think.

-- 
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] #2131: [patch] HttpResponseSendFile for serving static files handler-specific sendfile mechanism

2009-03-17 Thread Django

#2131: [patch] HttpResponseSendFile for serving static files handler-specific
sendfile mechanism
---+
  Reporter:  ymasuda[at]ethercube.com  | Owner:  alsleme 
Status:  new   | Milestone:  1.1 beta
 Component:  Core framework|   Version:  SVN 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  1 |   Needs_tests:  1   
Needs_better_patch:  1 |  
---+
Comment (by grahamd):

 Jacob: Okay. Only asked as wanted to make sure that the name of header
 used was going to be somehow configurable to allow for those header names
 used by other things like Apache/nginx and perlbal and not be X-Sendfile
 specific. 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] #2131: [patch] HttpResponseSendFile for serving static files handler-specific sendfile mechanism

2009-03-17 Thread Django

#2131: [patch] HttpResponseSendFile for serving static files handler-specific
sendfile mechanism
---+
  Reporter:  ymasuda[at]ethercube.com  | Owner:  alsleme 
Status:  new   | Milestone:  1.1 beta
 Component:  Core framework|   Version:  SVN 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  1 |   Needs_tests:  1   
Needs_better_patch:  1 |  
---+
Comment (by jacob):

 Graham: Yes, I'd expect to see x-sendfile support before I check this in.

 mrts: I explicitly asked asked that `HttpResponseSendFile` mimic standard
 `HttpResponse` semantics. This is a backwards-compatibility issue: writing
 custom handlers is an advanced but support feature.

-- 
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] #2131: [patch] HttpResponseSendFile for serving static files handler-specific sendfile mechanism

2009-03-17 Thread Django

#2131: [patch] HttpResponseSendFile for serving static files handler-specific
sendfile mechanism
---+
  Reporter:  ymasuda[at]ethercube.com  | Owner:  alsleme 
Status:  new   | Milestone:  1.1 beta
 Component:  Core framework|   Version:  SVN 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  1 |   Needs_tests:  1   
Needs_better_patch:  1 |  
---+
Changes (by grahamd):

 * cc: graham.dumple...@gmail.com (added)

Comment:

 Can someone indicate whether the intention is, or have these changes
 supported X-Sendfile as mentioned? I looked through some of the multitude
 of diffs, but couldn't see it mentioned.

-- 
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] r10080 - django/trunk/django/contrib/admin

2009-03-17 Thread noreply


Author: jacob
Date: 2009-03-17 22:03:24 -0500 (Tue, 17 Mar 2009)
New Revision: 10080

Modified:
   django/trunk/django/contrib/admin/validation.py
Log:
Fixed #10530, #10527: added a couple more validation errors around 
`list_editable`. Thanks, Florian Apolloner.

Modified: django/trunk/django/contrib/admin/validation.py
===
--- django/trunk/django/contrib/admin/validation.py 2009-03-18 01:08:34 UTC 
(rev 10079)
+++ django/trunk/django/contrib/admin/validation.py 2009-03-18 03:03:24 UTC 
(rev 10080)
@@ -71,21 +71,30 @@
 raise ImproperlyConfigured("'%s.list_editable' cannot be used "
 "without a default ordering. Please define ordering on either 
%s or %s."
 % (cls.__name__, cls.__name__, model.__name__))
-for idx, field in enumerate(cls.list_editable):
+for idx, field_name in enumerate(cls.list_editable):
 try:
-opts.get_field_by_name(field)
+field = opts.get_field_by_name(field_name)[0]
 except models.FieldDoesNotExist:
 raise ImproperlyConfigured("'%s.list_editable[%d]' refers to a 
"
-"field, '%s', not defiend on %s." % (cls.__name__, idx, 
field, model.__name__))
-if field not in cls.list_display:
+"field, '%s', not defiend on %s." 
+% (cls.__name__, idx, field_name, model.__name__))
+if field_name not in cls.list_display:
 raise ImproperlyConfigured("'%s.list_editable[%d]' refers to "
 "'%s' which is not defined in 'list_display'."
-% (cls.__name__, idx, field))
-if field in cls.list_display_links:
+% (cls.__name__, idx, field_name))
+if field_name in cls.list_display_links:
 raise ImproperlyConfigured("'%s' cannot be in both 
'%s.list_editable'"
 " and '%s.list_display_links'"
-% (field, cls.__name__, cls.__name__))
-
+% (field_name, cls.__name__, cls.__name__))
+if not cls.list_display_links and cls.list_display[0] in 
cls.list_editable:
+raise ImproperlyConfigured("'%s.list_editable[%d]' refers to"
+" the first field in list_display, '%s', which can't be"
+" used unless list_display_links is set." 
+% (cls.__name__, idx, cls.list_display[0]))
+if not field.editable:
+raise ImproperlyConfigured("'%s.list_editable[%d]' refers to a 
"
+"field, '%s', which isn't editable through the admin."
+% (cls.__name__, idx, field_name))
 
 # search_fields = ()
 if hasattr(cls, 'search_fields'):


--~--~-~--~~~---~--~~
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] #10061: incorrect logout link in admin

2009-03-17 Thread Django

#10061: incorrect logout link in admin
---+
  Reporter:  lashni| Owner:  Alex
Status:  reopened  | Milestone:  1.1 
 Component:  django.contrib.admin  |   Version:  SVN 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Comment (by treworld):

 '''To fix this problem:'''

 1) Open django_directory/contrib/admin/sites.py.

 2) Find "self.root_path = 'admin/'" (around line 41).

 3) Replace it with "self.root_path = '/admin/'".

 4) Save and restart your app/server.

-- 
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] #10134: unique_for_* broken?

2009-03-17 Thread Django

#10134: unique_for_* broken?
---+
  Reporter:  wdoekes   | Owner:  nobody 
 
Status:  new   | Milestone:  1.1
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  
unique_for_date unique_for_month unique_for_year
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

 * cc: flo...@gmail.com (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] #10526: Django INSTALLED_APPS with '.*' processing too stingy

2009-03-17 Thread Django

#10526: Django INSTALLED_APPS with '.*' processing too stingy
-+--
  Reporter:  Alex| Owner:  nobody
Status:  closed  | Milestone:  1.1   
 Component:  Core framework  |   Version:  SVN   
Resolution:  fixed   |  Keywords:
 Stage:  Accepted| Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by mtredinnick):

 Gargh. The two referenced commits should have been r9994 and r9995, in
 case anybody is following this up at a later date.

-- 
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] r10079 - in django/branches/releases/1.0.X: django/conf tests/regressiontests/app_loading tests/regressiontests/app_loading/parent tests/regressiontests/app_loading/parent/app tests/regres

2009-03-17 Thread noreply


Author: mtredinnick
Date: 2009-03-17 20:08:34 -0500 (Tue, 17 Mar 2009)
New Revision: 10079

Added:
   
django/branches/releases/1.0.X/tests/regressiontests/app_loading/parent/app_2/
   
django/branches/releases/1.0.X/tests/regressiontests/app_loading/parent/app_2/__init__.py
Modified:
   django/branches/releases/1.0.X/django/conf/__init__.py
   
django/branches/releases/1.0.X/tests/regressiontests/app_loading/parent/__init__.py
   
django/branches/releases/1.0.X/tests/regressiontests/app_loading/parent/app/__init__.py
   
django/branches/releases/1.0.X/tests/regressiontests/app_loading/parent/app1/__init__.py
   django/branches/releases/1.0.X/tests/regressiontests/app_loading/tests.py
Log:
Fixed #10526 -- More fixes when specifying installed apps using "foo.*".

This adds a case that was missed in r9925: underscore handling.

Backport of r10078 from trunk.

Modified: django/branches/releases/1.0.X/django/conf/__init__.py
===
--- django/branches/releases/1.0.X/django/conf/__init__.py  2009-03-18 
00:59:40 UTC (rev 10078)
+++ django/branches/releases/1.0.X/django/conf/__init__.py  2009-03-18 
01:08:34 UTC (rev 10079)
@@ -7,6 +7,7 @@
 """
 
 import os
+import re
 import time # Needed for Windows
 
 from django.conf import global_settings
@@ -91,8 +92,9 @@
 appdir = os.path.dirname(__import__(app[:-2], {}, {}, 
['']).__file__)
 app_subdirs = os.listdir(appdir)
 app_subdirs.sort()
+name_pattern = re.compile(r'[a-zA-Z]\w*')
 for d in app_subdirs:
-if d.isalnum() and d[0].isalpha() and 
os.path.isdir(os.path.join(appdir, d)):
+if name_pattern.match(d) and 
os.path.isdir(os.path.join(appdir, d)):
 new_installed_apps.append('%s.%s' % (app[:-2], d))
 else:
 new_installed_apps.append(app)

Modified: 
django/branches/releases/1.0.X/tests/regressiontests/app_loading/parent/__init__.py
===
--- 
django/branches/releases/1.0.X/tests/regressiontests/app_loading/parent/__init__.py
 2009-03-18 00:59:40 UTC (rev 10078)
+++ 
django/branches/releases/1.0.X/tests/regressiontests/app_loading/parent/__init__.py
 2009-03-18 01:08:34 UTC (rev 10079)
@@ -1 +0,0 @@
-# not empty to make SVN happy

Modified: 
django/branches/releases/1.0.X/tests/regressiontests/app_loading/parent/app/__init__.py
===
--- 
django/branches/releases/1.0.X/tests/regressiontests/app_loading/parent/app/__init__.py
 2009-03-18 00:59:40 UTC (rev 10078)
+++ 
django/branches/releases/1.0.X/tests/regressiontests/app_loading/parent/app/__init__.py
 2009-03-18 01:08:34 UTC (rev 10079)
@@ -1 +0,0 @@
-# not empty to make SVN happy

Modified: 
django/branches/releases/1.0.X/tests/regressiontests/app_loading/parent/app1/__init__.py
===
--- 
django/branches/releases/1.0.X/tests/regressiontests/app_loading/parent/app1/__init__.py
2009-03-18 00:59:40 UTC (rev 10078)
+++ 
django/branches/releases/1.0.X/tests/regressiontests/app_loading/parent/app1/__init__.py
2009-03-18 01:08:34 UTC (rev 10079)
@@ -1 +0,0 @@
-# not empty to make SVN happy

Added: 
django/branches/releases/1.0.X/tests/regressiontests/app_loading/parent/app_2/__init__.py
===

Modified: 
django/branches/releases/1.0.X/tests/regressiontests/app_loading/tests.py
===
--- django/branches/releases/1.0.X/tests/regressiontests/app_loading/tests.py   
2009-03-18 00:59:40 UTC (rev 10078)
+++ django/branches/releases/1.0.X/tests/regressiontests/app_loading/tests.py   
2009-03-18 01:08:34 UTC (rev 10079)
@@ -14,7 +14,7 @@
 >>> settings = Settings('test_settings')
 
 >>> settings.INSTALLED_APPS
-['parent.app', 'parent.app1']
+['parent.app', 'parent.app1', 'parent.app_2']
 
 >>> sys.path = old_sys_path
 


--~--~-~--~~~---~--~~
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] r10078 - in django/trunk: django/conf tests/regressiontests/app_loading tests/regressiontests/app_loading/parent tests/regressiontests/app_loading/parent/app tests/regressiontests/app_load

2009-03-17 Thread noreply


Author: mtredinnick
Date: 2009-03-17 19:59:40 -0500 (Tue, 17 Mar 2009)
New Revision: 10078

Added:
   django/trunk/tests/regressiontests/app_loading/parent/app_2/
   django/trunk/tests/regressiontests/app_loading/parent/app_2/__init__.py
Modified:
   django/trunk/django/conf/__init__.py
   django/trunk/tests/regressiontests/app_loading/parent/__init__.py
   django/trunk/tests/regressiontests/app_loading/parent/app/__init__.py
   django/trunk/tests/regressiontests/app_loading/parent/app1/__init__.py
   django/trunk/tests/regressiontests/app_loading/tests.py
Log:
Fixed #10526 -- More fixes when specifying installed apps using "foo.*".

This adds a case that was missed in r9924: underscore handling.

Modified: django/trunk/django/conf/__init__.py
===
--- django/trunk/django/conf/__init__.py2009-03-17 20:51:47 UTC (rev 
10077)
+++ django/trunk/django/conf/__init__.py2009-03-18 00:59:40 UTC (rev 
10078)
@@ -7,6 +7,7 @@
 """
 
 import os
+import re
 import time # Needed for Windows
 
 from django.conf import global_settings
@@ -91,8 +92,9 @@
 appdir = os.path.dirname(__import__(app[:-2], {}, {}, 
['']).__file__)
 app_subdirs = os.listdir(appdir)
 app_subdirs.sort()
+name_pattern = re.compile(r'[a-zA-Z]\w*')
 for d in app_subdirs:
-if d.isalnum() and d[0].isalpha() and 
os.path.isdir(os.path.join(appdir, d)):
+if name_pattern.match(d) and 
os.path.isdir(os.path.join(appdir, d)):
 new_installed_apps.append('%s.%s' % (app[:-2], d))
 else:
 new_installed_apps.append(app)

Modified: django/trunk/tests/regressiontests/app_loading/parent/__init__.py
===
--- django/trunk/tests/regressiontests/app_loading/parent/__init__.py   
2009-03-17 20:51:47 UTC (rev 10077)
+++ django/trunk/tests/regressiontests/app_loading/parent/__init__.py   
2009-03-18 00:59:40 UTC (rev 10078)
@@ -1 +0,0 @@
-# not empty to make SVN happy

Modified: django/trunk/tests/regressiontests/app_loading/parent/app/__init__.py
===
--- django/trunk/tests/regressiontests/app_loading/parent/app/__init__.py   
2009-03-17 20:51:47 UTC (rev 10077)
+++ django/trunk/tests/regressiontests/app_loading/parent/app/__init__.py   
2009-03-18 00:59:40 UTC (rev 10078)
@@ -1 +0,0 @@
-# not empty to make SVN happy

Modified: django/trunk/tests/regressiontests/app_loading/parent/app1/__init__.py
===
--- django/trunk/tests/regressiontests/app_loading/parent/app1/__init__.py  
2009-03-17 20:51:47 UTC (rev 10077)
+++ django/trunk/tests/regressiontests/app_loading/parent/app1/__init__.py  
2009-03-18 00:59:40 UTC (rev 10078)
@@ -1 +0,0 @@
-# not empty to make SVN happy

Added: django/trunk/tests/regressiontests/app_loading/parent/app_2/__init__.py
===

Modified: django/trunk/tests/regressiontests/app_loading/tests.py
===
--- django/trunk/tests/regressiontests/app_loading/tests.py 2009-03-17 
20:51:47 UTC (rev 10077)
+++ django/trunk/tests/regressiontests/app_loading/tests.py 2009-03-18 
00:59:40 UTC (rev 10078)
@@ -14,7 +14,7 @@
 >>> settings = Settings('test_settings')
 
 >>> settings.INSTALLED_APPS
-['parent.app', 'parent.app1']
+['parent.app', 'parent.app1', 'parent.app_2']
 
 >>> sys.path = old_sys_path
 


--~--~-~--~~~---~--~~
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] #10427: Bound field needs an easy way to get form value

2009-03-17 Thread Django

#10427: Bound field needs an easy way to get form value
---+
  Reporter:  toxik | Owner:  nobody  
Status:  reopened  | Milestone:  
 Component:  Forms |   Version:  SVN 
Resolution:|  Keywords:  form field value
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by toxik):

  * needs_better_patch:  1 => 0
  * needs_docs:  1 => 0

Comment:

 I'm very sorry about attaching this massive amount of patches, but I
 figured using "replace existing" when there are already renamed patches
 would get confusing.

 Replying to [comment:6 mtredinnick]:
 > Calling a function using parentheses doesn't look at all weird. Normal
 code doesn't need to access the data attribute (yes, it should also have
 been a method) on a `BoundField`, so that's not particular relevant in the
 public API.

 Yeah, sure, but then it should really be a verb/verb+noun, and not a noun.
 Like "get_value". I don't see the big win in adding asymmetry and yet not
 gaining anything; it could just as well be an actual instance attribute
 (and probably should be?)

 Bikeshed away, however.

-- 
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] #10526: Django INSTALLED_APPS with '.*' processing too stingy

2009-03-17 Thread Django

#10526: Django INSTALLED_APPS with '.*' processing too stingy
-+--
  Reporter:  Alex| Owner:  nobody
Status:  new | Milestone:  1.1   
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by mtredinnick):

  * milestone:  => 1.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] #10526: Django INSTALLED_APPS with '.*' processing too stingy

2009-03-17 Thread Django

#10526: Django INSTALLED_APPS with '.*' processing too stingy
-+--
  Reporter:  Alex| Owner:  nobody
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 mtredinnick):

  * version:  1.0 => SVN
  * stage:  Unreviewed => Accepted

Comment:

 Looks like a variant on the fix that went in for #9323. This is valid.

-- 
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] #10505: Integrate django-batchadmin

2009-03-17 Thread Django

#10505: Integrate django-batchadmin
---+
  Reporter:  jezdez| Owner:  jacob   
Status:  new   | Milestone:  1.1 beta
 Component:  django.contrib.admin  |   Version:  SVN 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  1 |   Needs_tests:  1   
Needs_better_patch:  0 |  
---+
Comment (by jezdez):

 Oh, the last patch also includes a better default delete action that will
 ask for confirmation before deleting, courtesy of Martin Mahner.

-- 
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] #10531: Choices template display example needed

2009-03-17 Thread Django

#10531: Choices template display example needed
---+
 Reporter:  paulbury   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Descriptions of how to get the template to display choices value not the
 data value were really vague. it wasn't until after i did a bunch opf
 googling that i found how to do it:

 {{object.get_FOO_display}}

 Having this example somewhere in the doc's would be usefull. Possibly
 under either the choices doco or under the get_FOO_display doco.

 Regards

 Paul

-- 
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] #10530: list_editable and list_display[0] clashes

2009-03-17 Thread Django

#10530: list_editable and list_display[0] clashes
---+
  Reporter:  apollo13  | Owner:  nobody
Status:  new   | Milestone:  1.1   
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Ready for checkin | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

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

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #10526: Django INSTALLED_APPS with '.*' processing too stingy

2009-03-17 Thread Django

#10526: Django INSTALLED_APPS with '.*' processing too stingy
-+--
  Reporter:  Alex| Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  1.0   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by Alex):

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

Old description:

> Specifically it doesn't include any apps with underscores in their names.

New description:

 When django sees an app in INSTALLED apps with .* it expands that to
 include all apps in that directory.  However it omits any apps with '_' in
 their names.

Comment:

 Describe the problem 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
-~--~~~~--~~--~--~---

[Django] #10530: list_editable and list_display[0] clashes

2009-03-17 Thread Django

#10530: list_editable and list_display[0] clashes
--+-
 Reporter:  apollo13  |   Owner:  nobody
   Status:  new   |   Milestone:  1.1   
Component:  django.contrib.admin  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 if list_display_links isn't set, the first field of list_display is used
 for the links. If this field is used in list_editable then, the current
 validation doesn't catches it.

-- 
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] #10529: Generic Inline fails (unexpected keyword argument `prefix`)

2009-03-17 Thread Django

#10529: Generic Inline fails (unexpected keyword argument `prefix`)
-+--
  Reporter:  leitjohn| Owner:  leitjohn
Status:  new | Milestone:  
 Component:  Forms   |   Version:  SVN 
Resolution:  |  Keywords:  
 Stage:  Unreviewed  | Has_patch:  0   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by Alex):

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

Comment:

 
http://code.djangoproject.com/browser/django/trunk/django/contrib/contenttypes/generic.py#L287
 correctly accepts a prefix argument so I'm not sure what your problem
 might be.  I'll leave this open if you can provide some more open.

-- 
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] #10529: Generic Inline fails (unexpected keyword argument `prefix`)

2009-03-17 Thread Django

#10529: Generic Inline fails (unexpected keyword argument `prefix`)
--+-
 Reporter:  leitjohn  |   Owner:  leitjohn  
   Status:  new   |   Milestone:
Component:  Forms | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 I got a type exception saying, "__init__() got an unexpected keyword
 argument 'prefix'"

 I found out that it was caused by a GenericTabularInline, for when i
 commented it out the error went away. I'm running the latest SVN so i
 guess it's to be expected.

 Don't all forms allow the "prefix" keyword?

 I'll try to get a patch for it soon.

-- 
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] #10528: Admin documentation doesn't mention reverse names

2009-03-17 Thread Django

#10528: Admin documentation doesn't mention reverse names
+---
  Reporter:  Leo| Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Alex):

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

Comment:

 This is fixed in my github branch here:
 http://github.com/alex/django/commits/admin-url (and in the patch on
 #10061) leaving this open to track the issue.

-- 
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] #10528: Admin documentation doesn't mention reverse names

2009-03-17 Thread Django

#10528: Admin documentation doesn't mention reverse names
+---
  Reporter:  Leo| Owner:  nobody
Status:  new| Milestone:  1.1   
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Alex):

  * stage:  Unreviewed => Accepted
  * milestone:  => 1.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
-~--~~~~--~~--~--~---

[Django] #10528: Admin documentation doesn't mention reverse names

2009-03-17 Thread Django

#10528: Admin documentation doesn't mention reverse names
---+
 Reporter:  Leo|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 The admin page URL's are accessible from reverse and the {% url %} tag as
 detailed in this blog entry: http://www.codekoala.com/blog/2009/feb/24
 /pluggable-django-apps-and-djangos-admin/

 The fact that the admin views are named (and what the naming structure is)
 isn't documented anywhere in the docs.

-- 
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] #10527: list_editable fails if field is not editable

2009-03-17 Thread Django

#10527: list_editable fails if field is not editable
---+
  Reporter:  apollo13  | Owner:  nobody
Status:  new   | Milestone:  1.1   
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Ready for checkin | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

  * needs_better_patch:  => 0
  * needs_docs:  => 0
  * stage:  Unreviewed => Ready for checkin
  * needs_tests:  => 0
  * milestone:  1.1 beta => 1.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] #6218: Require trailing slash always on MEDIA_URL

2009-03-17 Thread Django

#6218: Require trailing slash always on MEDIA_URL
+---
  Reporter:  Michael Toomim   | 
Owner:   
Status:  new| 
Milestone:   
 Component:  Core framework |   
Version:  SVN  
Resolution: |  
Keywords:  easy-pickings
 Stage:  Accepted   | 
Has_patch:  1
Needs_docs:  0  |   
Needs_tests:  0
Needs_better_patch:  1  |  
+---
Changes (by Leo):

  * owner:  Leo =>
  * status:  assigned => new

-- 
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] #10527: list_editable fails if field is not editable

2009-03-17 Thread Django

#10527: list_editable fails if field is not editable
--+-
 Reporter:  apollo13  |   Owner:  nobody
   Status:  new   |   Milestone:  1.1 beta  
Component:  django.contrib.admin  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 list_editable fails if the requested field isn't editable via the admin
 interface, like:
 {{{
 creation_date = models.DatetimeField(auto_now_add=True)
 }}}
 To prevent those errors, I added another validation check which ensures
 the field __is__ editable.

-- 
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] #5605: Username email address part is case sensitive

2009-03-17 Thread Django

#5605: Username email address part is case sensitive
--+-
  Reporter:  m.ga...@paranoja.pl  | Owner:  Leo 
 
Status:  assigned | Milestone:  
 
 Component:  Contrib apps |   Version:  SVN 
 
Resolution:   |  Keywords:  auth email lowerase 
easy-pickings
 Stage:  Accepted | Has_patch:  1   
 
Needs_docs:  0|   Needs_tests:  0   
 
Needs_better_patch:  0|  
--+-
Changes (by Leo):

  * needs_better_patch:  1 => 0

Comment:

 Thanks brodie, removing needs better patch flag.

-- 
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] #10526: Django INSTALLED_APPS with '.*' processing too stingy

2009-03-17 Thread Django

#10526: Django INSTALLED_APPS with '.*' processing too stingy
+---
 Reporter:  Alex|   Owner:  nobody
   Status:  new |   Milestone:
Component:  Core framework  | Version:  1.0   
 Keywords:  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 Specifically it doesn't include any apps with underscores in their names.

-- 
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] r10077 - in django/trunk: django/contrib/admin django/contrib/admin/templates/admin django/contrib/admin/templatetags django/contrib/admin/views docs/ref/contrib tests/regressiontests/admi

2009-03-17 Thread noreply


Author: jacob
Date: 2009-03-17 15:51:47 -0500 (Tue, 17 Mar 2009)
New Revision: 10077

Added:
   
django/trunk/tests/regressiontests/admin_views/fixtures/admin-views-person.xml
Modified:
   django/trunk/django/contrib/admin/options.py
   django/trunk/django/contrib/admin/templates/admin/change_list.html
   django/trunk/django/contrib/admin/templates/admin/pagination.html
   django/trunk/django/contrib/admin/templatetags/admin_list.py
   django/trunk/django/contrib/admin/validation.py
   django/trunk/django/contrib/admin/views/main.py
   django/trunk/docs/ref/contrib/admin.txt
   django/trunk/tests/regressiontests/admin_views/models.py
   django/trunk/tests/regressiontests/admin_views/tests.py
Log:
Fixed #8939: added a `list_editable` option to `ModelAdmin`; fields declared 
`list_editable` may be edited, in bulk, on the changelist page. Thanks, Alex 
Gaynor.

Modified: django/trunk/django/contrib/admin/options.py
===
--- django/trunk/django/contrib/admin/options.py2009-03-17 20:51:06 UTC 
(rev 10076)
+++ django/trunk/django/contrib/admin/options.py2009-03-17 20:51:47 UTC 
(rev 10077)
@@ -1,6 +1,6 @@
 from django import forms, template
 from django.forms.formsets import all_valid
-from django.forms.models import modelform_factory, inlineformset_factory
+from django.forms.models import modelform_factory, modelformset_factory, 
inlineformset_factory
 from django.forms.models import BaseInlineFormSet
 from django.contrib.contenttypes.models import ContentType
 from django.contrib.admin import widgets
@@ -16,6 +16,7 @@
 from django.utils.functional import curry
 from django.utils.text import capfirst, get_text_list
 from django.utils.translation import ugettext as _
+from django.utils.translation import ngettext
 from django.utils.encoding import force_unicode
 try:
 set
@@ -108,7 +109,7 @@
 if db_field.__class__ in self.formfield_overrides:
 kwargs = dict(self.formfield_overrides[db_field.__class__], 
**kwargs)
 return db_field.formfield(**kwargs)
-
+
 # For any other type of field, just call its formfield() method.
 return db_field.formfield(**kwargs)
 
@@ -177,6 +178,7 @@
 list_filter = ()
 list_select_related = False
 list_per_page = 100
+list_editable = ()
 search_fields = ()
 date_hierarchy = None
 save_as = False
@@ -313,6 +315,29 @@
 defaults.update(kwargs)
 return modelform_factory(self.model, **defaults)
 
+def get_changelist_form(self, request, **kwargs):
+"""
+Returns a Form class for use in the Formset on the changelist page.
+"""
+defaults = {
+"formfield_callback": curry(self.formfield_for_dbfield, 
request=request),
+}
+defaults.update(kwargs)
+return modelform_factory(self.model, **defaults)
+
+def get_changelist_formset(self, request, **kwargs):
+"""
+Returns a FormSet class for use on the changelist page if 
list_editable 
+is used.
+"""
+defaults = {
+"formfield_callback": curry(self.formfield_for_dbfield, 
request=request),
+}
+defaults.update(kwargs)
+return modelformset_factory(self.model, 
+self.get_changelist_form(request), extra=0, 
+fields=self.list_editable, **defaults)
+
 def get_formsets(self, request, obj=None):
 for inline in self.inline_instances:
 yield inline.get_formset(request, obj)
@@ -685,7 +710,7 @@
 raise PermissionDenied
 try:
 cl = ChangeList(request, self.model, self.list_display, 
self.list_display_links, self.list_filter,
-self.date_hierarchy, self.search_fields, 
self.list_select_related, self.list_per_page, self)
+self.date_hierarchy, self.search_fields, 
self.list_select_related, self.list_per_page, self.list_editable, self)
 except IncorrectLookupParameters:
 # Wacky lookup parameters were given, so redirect to the main
 # changelist page, without parameters, and pass an 'invalid=1'
@@ -696,10 +721,53 @@
 return render_to_response('admin/invalid_setup.html', 
{'title': _('Database error')})
 return HttpResponseRedirect(request.path + '?' + ERROR_FLAG + '=1')
 
+# If we're allowing changelist editing, we need to construct a formset
+# for the changelist given all the fields to be edited. Then we'll
+# use the formset to validate/process POSTed data.
+formset = cl.formset = None
+
+# Handle POSTed bulk-edit data.
+if request.method == "POST" and self.list_editable:
+FormSet = self.get_changelist_formset(request)
+formset = cl.formset = FormSet(request.POST, request.FILES, 
queryset=cl.result_list)
+if formset.is_valid():

[Changeset] r10076 - in django/branches/releases/1.0.X: . django/contrib/admin

2009-03-17 Thread noreply


Author: jacob
Date: 2009-03-17 15:51:06 -0500 (Tue, 17 Mar 2009)
New Revision: 10076

Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/django/contrib/admin/sites.py
Log:
[1.0.X]  `ModelAdmin` validation now runs when using the `site.register(Model, 
**kwargs)` form.

Backport if [10074] from trunk.



Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10009,10013,10015,10017,10022,10024,10049,10051,10073
   + 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10009,10013,10015,10017,10022,10024,10049,10051,10073-10074

Modified: django/branches/releases/1.0.X/django/contrib/admin/sites.py
===
--- django/branches/releases/1.0.X/django/contrib/admin/sites.py
2009-03-17 20:47:47 UTC (rev 10075)
+++ django/branches/releases/1.0.X/django/contrib/admin/sites.py
2009-03-17 20:51:06 UTC (rev 10076)
@@ -49,14 +49,15 @@
 
 If a model is already registered, this will raise AlreadyRegistered.
 """
+if not admin_class:
+admin_class = ModelAdmin
+
 # Don't import the humongous validation code unless required
 if admin_class and settings.DEBUG:
 from django.contrib.admin.validation import validate
 else:
 validate = lambda model, adminclass: None
 
-if not admin_class:
-admin_class = ModelAdmin
 if isinstance(model_or_iterable, ModelBase):
 model_or_iterable = [model_or_iterable]
 for model in model_or_iterable:


--~--~-~--~~~---~--~~
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] r10075 - in django/branches/releases/1.0.X: . django/forms

2009-03-17 Thread noreply


Author: jacob
Date: 2009-03-17 15:47:47 -0500 (Tue, 17 Mar 2009)
New Revision: 10075

Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/django/forms/formsets.py
Log:
[1.0.X] Fixed `BaseFormSet.is_multipart()` so that it doesn't bomb when called 
on an empty formset. 

Backport of [10073] from trunk.



Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10009,10013,10015,10017,10022,10024,10049,10051
   + 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10009,10013,10015,10017,10022,10024,10049,10051,10073

Modified: django/branches/releases/1.0.X/django/forms/formsets.py
===
--- django/branches/releases/1.0.X/django/forms/formsets.py 2009-03-17 
20:40:01 UTC (rev 10074)
+++ django/branches/releases/1.0.X/django/forms/formsets.py 2009-03-17 
20:47:47 UTC (rev 10075)
@@ -258,7 +258,7 @@
 Returns True if the formset needs to be multipart-encrypted, i.e. it
 has FileInput. Otherwise, False.
 """
-return self.forms[0].is_multipart()
+return self.forms and self.forms[0].is_multipart()
 
 def _get_media(self):
 # All the forms on a FormSet are the same, so you only need to


--~--~-~--~~~---~--~~
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] r10074 - django/trunk/django/contrib/admin

2009-03-17 Thread noreply


Author: jacob
Date: 2009-03-17 15:40:01 -0500 (Tue, 17 Mar 2009)
New Revision: 10074

Modified:
   django/trunk/django/contrib/admin/sites.py
Log:
`ModelAdmin` validation now runs when using the `site.register(Model, 
**kwargs)` form.

Modified: django/trunk/django/contrib/admin/sites.py
===
--- django/trunk/django/contrib/admin/sites.py  2009-03-17 19:23:23 UTC (rev 
10073)
+++ django/trunk/django/contrib/admin/sites.py  2009-03-17 20:40:01 UTC (rev 
10074)
@@ -57,14 +57,15 @@
 
 If a model is already registered, this will raise AlreadyRegistered.
 """
+if not admin_class:
+admin_class = ModelAdmin
+
 # Don't import the humongous validation code unless required
 if admin_class and settings.DEBUG:
 from django.contrib.admin.validation import validate
 else:
 validate = lambda model, adminclass: None
 
-if not admin_class:
-admin_class = ModelAdmin
 if isinstance(model_or_iterable, ModelBase):
 model_or_iterable = [model_or_iterable]
 for model in model_or_iterable:


--~--~-~--~~~---~--~~
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] #6903: Go back to old change_list view after hitting save

2009-03-17 Thread Django

#6903: Go back to old change_list view after hitting save
-+--
  Reporter:  jarrow  | Owner:  ramiro
Status:  new | Milestone:  1.1   
 Component:  django.contrib.admin|   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by ramiro):

 Replying to [comment:17 mawimawi]:
 > Isn't such a "sticky" behaviour exactly what sessions are for? Why would
 you not use a session key like
 > `request.session['admin_' +  + '_' +  + '_filter'] =
 {'p':14, 'my_field__exact':True}`
 > and checking for this key when displaying the list of objects of a
 model?
 >
 > I'm also offering to try and implement that if this is desired.

 I'd say got for it and attach it to the ticket so both implementations are
 available for review and the chances of this feature being available in
 1.1 are 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] #10525: staff_member_required doesn't work for FormWizard / call()

2009-03-17 Thread Django

#10525: staff_member_required doesn't work for FormWizard / __call__()
---+
  Reporter:  Alpha1650 | Owner:  nobody 
  
Status:  new   | Milestone: 
  
 Component:  django.contrib.admin  |   Version:  SVN
  
Resolution:|  Keywords:  
staff_member_required, FormWizard
 Stage:  Unreviewed| Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Comment (by anonymous):

 Replying to [comment:1 Alex]:
 > You've got an immense amount of code duplication here(plus this same
 issue will be true for any other decorator), so I think a cleaner solution
 is needed.

 I totally agree with you. I couldn't find a better solution. Maybe anyone
 else with better Python knowledge can. Maybe there's a general way to
 apply "normal" decorators to methods.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] r10073 - django/trunk/django/forms

2009-03-17 Thread noreply


Author: jacob
Date: 2009-03-17 14:23:23 -0500 (Tue, 17 Mar 2009)
New Revision: 10073

Modified:
   django/trunk/django/forms/formsets.py
Log:
Fixed `BaseFormSet.is_multipart()` so that it doesn't bomb when called on an 
empty formset.

Modified: django/trunk/django/forms/formsets.py
===
--- django/trunk/django/forms/formsets.py   2009-03-17 16:13:09 UTC (rev 
10072)
+++ django/trunk/django/forms/formsets.py   2009-03-17 19:23:23 UTC (rev 
10073)
@@ -258,7 +258,7 @@
 Returns True if the formset needs to be multipart-encrypted, i.e. it
 has FileInput. Otherwise, False.
 """
-return self.forms[0].is_multipart()
+return self.forms and self.forms[0].is_multipart()
 
 def _get_media(self):
 # All the forms on a FormSet are the same, so you only need to


--~--~-~--~~~---~--~~
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] #10521: Test failure of missing url '/' in test django.contrib.auth.tests.remote_user.py

2009-03-17 Thread Django

#10521: Test failure of missing url '/' in test
django.contrib.auth.tests.remote_user.py
-+--
  Reporter:  kegan   | Owner:  nobody
Status:  reopened| Milestone:
 Component:  Authentication  |   Version:
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by ramiro):

  * has_patch:  0 => 1

Comment:

 The attached patch implements changes to the new tests so they run
 successfully not only as part of the Django test suite but also when the
 auth app is in `INSTALLED_APPS` and `manage.py test` is used in a project.

 Something the patch can't express (but could be implemented with a `svn
 mv` instead) is that the `django/contrib/auth/tests/views.py` gets renamed
 to `django/contrib/auth/tests/views_tests.py`.

-- 
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] #10525: staff_member_required doesn't work for FormWizard / call()

2009-03-17 Thread Django

#10525: staff_member_required doesn't work for FormWizard / __call__()
---+
  Reporter:  Alpha1650 | Owner:  nobody 
  
Status:  new   | Milestone: 
  
 Component:  django.contrib.admin  |   Version:  SVN
  
Resolution:|  Keywords:  
staff_member_required, FormWizard
 Stage:  Unreviewed| Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by Alex):

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

Comment:

 You've got an immense amount of code duplication here(plus this same issue
 will be true for any other decorator), so I think a cleaner solution is
 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
-~--~~~~--~~--~--~---

[Django] #10525: staff_member_required doesn't work for FormWizard / call()

2009-03-17 Thread Django

#10525: staff_member_required doesn't work for FormWizard / __call__()
---+
 Reporter:  Alpha1650  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  django.contrib.admin   | Version:  SVN   
 Keywords:  staff_member_required, FormWizard  |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 Hi,

 The "staff_member_required" decorator doesn't work for FormWizard or in
 general for decorating methods as for example _ _call_ _(). That's because
 the decorator expects the first argument to be a request instance but with
 methods the first argument is self and the second argument is the request
 object.

 The patch changes this by adding a check whether the object to be
 decorated is a function or a method. Then it decorates the appropriate
 way.

 In order to decorate FormWizard's _ _call_ _() you have to do this:

 {{{

 from django.contrib.formtools.wizard import FormWizard
 from django.contrib.admin.views.decorators import staff_member_required

 class Wizard(FormWizard):
 # ...
 pass

 Wizard.__call__ = staff_member_required(Wizard.__call__)
 }}}

 I added my changes as a patch.

 Alpha1650

-- 
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] #4465: Invalid sql string formatting (TypeError) if sql contains '%' signs in /django/db/backends/util.py

2009-03-17 Thread Django

#4465: Invalid sql string formatting (TypeError) if sql contains '%' signs in
/django/db/backends/util.py
---+
  Reporter:  MockSoul  | Owner:  adrian
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  0.96  
Resolution:  duplicate |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by sneakeralley):

 Anybody knows a good It Developer?

 [http://www.sneakeralley.com/Nike Air Force One]

-- 
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] #10524: Pagination via object_list generic view: Docs don't point out all the variables added to the context

2009-03-17 Thread Django

#10524: Pagination via object_list generic view: Docs don't point out all the
variables added to the context
+---
  Reporter:  Beetle_B   | Owner:  nobody
Status:  closed | Milestone:
 Component:  Generic views  |   Version:  1.0   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Alex):

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

Comment:

 Yep, these are legacy and hence not mentioned:
 
http://code.djangoproject.com/browser/django/trunk/django/views/generic/list_detail.py#L67

-- 
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] #10524: Pagination via object_list generic view: Docs don't point out all the variables added to the context

2009-03-17 Thread Django

#10524: Pagination via object_list generic view: Docs don't point out all the
variables added to the context
---+
 Reporter:  Beetle_B   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Generic views  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 When using pagination with the list_detait.object_list generic view, the
 following variables are added to the context:

 {{{
 previous
 next
 page
 has_next
 has_previous
 }}}

 and perhaps others. Yet, I don't see this documented anywhere. These are
 all methods of the Page object, and the generic view docs do say that
 page_obj is added to the context.

 If this is legacy behavior that will be removed, I'd really like to know
 so that I don't use them, and so that I explicitly use the page_obj
 methods.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #10512: Ordering of non-model fields in a ModelForm, after #8164

2009-03-17 Thread Django

#10512: Ordering of non-model fields in a ModelForm, after #8164
---+
  Reporter:  mbi   | Owner:  Alex  
Status:  closed| Milestone:
 Component:  Forms |   Version:  SVN   
Resolution:  fixed |  Keywords:  modelform, field order
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Comment (by Alex):

 Yes it does, the behavior of the SortedDict is that on update it doesn't
 reset the position of the key.  So basically what happens is it tries to
 get a non Model field, it doesn't find it, it puts a None in the
 fields_dict, then later that gets updated which keeps that key position.
 And the tests demonstrate 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] #10512: Ordering of non-model fields in a ModelForm, after #8164

2009-03-17 Thread Django

#10512: Ordering of non-model fields in a ModelForm, after #8164
---+
  Reporter:  mbi   | Owner:  Alex  
Status:  closed| Milestone:
 Component:  Forms |   Version:  SVN   
Resolution:  fixed |  Keywords:  modelform, field order
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Comment (by korpios):

 Alex: for the sake of ordering them.  The fix in r10070 doesn't address
 that.

-- 
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] #10523: Changing object with long repr causes error

2009-03-17 Thread Django

#10523: Changing object with long __repr__ causes error
---+
  Reporter:  bromer| Owner:  nobody
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

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

Comment:

 Can you provide the full traceback please?

-- 
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] #10523: Changing object with long repr causes error

2009-03-17 Thread Django

#10523: Changing object with long __repr__ causes error
--+-
 Reporter:  bromer|   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  1.0   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Editing an item in the django administration causes an DataError with the
 following message:

 {{{ value too long for type character varying(200) }}}

 I don't think the admin should explode, but rather cut the {{{
 object.__repr__() }}}

-- 
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] r10072 - in djangoproject.com: . djangodocs/templates/docs

2009-03-17 Thread noreply


Author: jacob
Date: 2009-03-17 11:13:09 -0500 (Tue, 17 Mar 2009)
New Revision: 10072

Added:
   djangoproject.com/fabfile.py
Modified:
   djangoproject.com/djangodocs/templates/docs/doc.html
Log:
[djangoproject.com] Correctly display the doc version in the sidebar 
breadcrumbs.

Modified: djangoproject.com/djangodocs/templates/docs/doc.html
===
--- djangoproject.com/djangodocs/templates/docs/doc.html2009-03-17 
10:40:04 UTC (rev 10071)
+++ djangoproject.com/djangodocs/templates/docs/doc.html2009-03-17 
16:13:09 UTC (rev 10072)
@@ -118,7 +118,7 @@
 
   {% block breadcrumbs %}
 
-  {{ 
env.docstitle }}
+  Django 
{{ version }} documentation
   {% for p in doc.parents %}
 {{ p.title|safe }}
   {% endfor %}

Added: djangoproject.com/fabfile.py
===
--- djangoproject.com/fabfile.py(rev 0)
+++ djangoproject.com/fabfile.py2009-03-17 16:13:09 UTC (rev 10072)
@@ -0,0 +1,12 @@
+config.fab_hosts = ['djangoproject.com']
+
+def deploy():
+sudo("cd /home/djangoproject.com && svn up")
+reload()
+
+def reload():
+sudo("invoke-rc.d apache2 reload")
+
+def flush_cache():
+sudo("invoke-rc.d memcached restart")
+


--~--~-~--~~~---~--~~
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] #9308: Django fails to set nullable foreign key field to NULL before deleting the referenced record

2009-03-17 Thread Django

#9308: Django fails to set nullable foreign key field to NULL before deleting 
the
referenced record
---+
  Reporter:  egenix_viktor | Owner:  nobody 
   
Status:  new   | Milestone:  1.1
   
 Component:  Database layer (models, ORM)  |   Version:  1.0
   
Resolution:|  Keywords:  delete 
record foreign key constraint check NULL nullable field
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Comment (by bthomas):

 Replying to [comment:14 liangent]:
 > i still have the question that why do we need this filter?
 It was added to fix #7778

-- 
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] #8336: runserver option for disabling admin static files serving

2009-03-17 Thread Django

#8336: runserver option for disabling admin static files serving
+---
  Reporter:  jakub_vysoky   | Owner:  nobody
   
Status:  closed | Milestone:
   
 Component:  django-admin.py runserver  |   Version:  SVN   
   
Resolution:  wontfix|  Keywords:  admin media 
runserver
 Stage:  Design decision needed | Has_patch:  1 
   
Needs_docs:  0  |   Needs_tests:  0 
   
Needs_better_patch:  0  |  
+---
Comment (by Almad):

 Ran into that too :]

-- 
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] #10521: Test failure of missing url '/' in test django.contrib.auth.tests.remote_user.py

2009-03-17 Thread Django

#10521: Test failure of missing url '/' in test
django.contrib.auth.tests.remote_user.py
-+--
  Reporter:  kegan   | Owner:  nobody
Status:  reopened| Milestone:
 Component:  Authentication  |   Version:
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by kegan):

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

Comment:

 I included django.contrib.auth in INSTALLED_APPS (settings.py of my
 project). When I run "./manage test", it inevitably run
 django.contrib.auth testcases (and testcases for all the other installed
 apps). This have been fine for all django.contrib apps ... since prior
 1.0. Now, I get errors for django.contrib.auth.

 Should I never run "./manage test" by itself, and must always specify app
 explicity?

 Replying to [comment:1 ramiro]:
 > You aren't supposed to run Django test suite tests using `manage.py`
 >
 > Closing as invalid because running `tests/runtests.py auth
 --verbosity=2` with an appropiate settings file shows the tests added in
 r10069 are run and don't generate error.

-- 
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] #10335: tzinfo.py should use getdefaultencoding instead of getdefaultlocale[1]

2009-03-17 Thread Django

#10335: tzinfo.py should use getdefaultencoding instead of getdefaultlocale[1]
-+--
  Reporter:  gthb| Owner:  nobody   
  
Status:  new | Milestone:  1.1  
  
 Component:  Core framework  |   Version:  1.0  
  
Resolution:  |  Keywords:  locale encoding 
getdefaultlocale getdefaultencoding mac
 Stage:  Accepted| Has_patch:  1
  
Needs_docs:  0   |   Needs_tests:  0
  
Needs_better_patch:  0   |  
-+--
Comment (by gthb):

 Sorry for the late reply, I hadn't set up an email address for
 notifications.

 In response to mtredinnick: good point about {{{setdefaultencoding}}}, I
 didn't know that. A few notes:

 1. The above patch (second one) only calls {{{getdefaultencoding}}}, and
 it does so only if the present implementation fails in a way that will
 break Django. The {{{setdefaultencoding}}} call would be made consciously
 by the user as a workaround, only upon encountering this problem, and they
 will only encounter it if {{{ascii}}} is not good enough.

 2. Based on a quick grep, this {{{DEFAULT_ENCODING}}} is used in only one
 place in all of Django, in this same file:
 {{{
 #!python
 return smart_unicode(time.tzname[self._isdst(dt)],
 DEFAULT_ENCODING)
 }}}
 Standard timezone names are probably all representable in {{{ascii}}}
 anyway, so maybe {{{ascii}}} is good enough here. I suppose
 {{{DEFAULT_ENCODING}}} (or timezones) must have been used in more places
 when I ran into this some weeks ago, because Django broke right away, but
 now it breaks only when I add something involving timezones. I now
 reproduce it with a view that does this:
 {{{
 #!python
 from django.utils.tzinfo import LocalTimezone
 from datetime import datetime
 LocalTimezone(datetime.now())
 }}}
 So maybe it is enough to settle for {{{ascii}}}, when the default locale
 method fails or returns a bogus encoding.

 3. I will attach a third, even more conservative patch, that just adds the
 codec lookup within the first try block. The trouble with Mac OS X in the
 Icelandic locale is that {{{locale.getdefaultlocale()[1]}}} ''does not
 raise an exception'' but instead just returns an encoding name that will
 result in an exception ''later'' when used. This most minimal patch just
 makes the failure come up right away, so that the {{{except}}} block deals
 with it. This way the comment "Any problems at all determining the locale
 and we fallback" is made more true, with no other effects.

 4. On correctness: the premise "since the user's system is set up to
 return their preference" assumes too much. My locale preference for the
 overall OS is not necessarily my locale preference for Django. In the case
 of Mac OS X I don't get to separate the two because of the hardcoding
 explained above. And if my preference is a locale with a Mac-specific
 encoding not recognized by Python (such as the Icelandic locale), then
 that triggers a serious problem in {{{django.utils.tzinfo}}}. The problem
 is not that ''Django'' doesn't understand the answer, but that ''Python
 itself'' doesn't. This problem can be worked around with one of the
 options I propose here.

-- 
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] #9480: django.test.client.FakePayload is truncating files

2009-03-17 Thread Django

#9480: django.test.client.FakePayload is truncating files
+---
  Reporter:  hellhound  | Owner:  nobody
  
Status:  closed | Milestone:  1.1   
  
 Component:  Testing framework  |   Version:  1.0   
  
Resolution:  worksforme |  Keywords:  FakePayload file post 
client
 Stage:  Accepted   | Has_patch:  0 
  
Needs_docs:  0  |   Needs_tests:  0 
  
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 I can't reproduce this failure. Using the following view:
 {{{
 def file_upload_view(request):
 "A view that validates integrity of file uploads"
 return render_to_response('base.html', {
 'file': request.FILES['file']
 })
 }}}

 the following test case passes without error:
 {{{
 class FileUploadTests(TestCase):
 def test_upload(self):
 testfile = os.path.join(os.path.dirname(__file__), 'fixtures',
 'testdata.json')
 f = open(testfile)
 response = self.client.post('/test_client_regress/file_test/',
 {'file': f})
 f.close()

 self.assertEqual(response.context['file'].size,
 os.stat(testfile).st_size)
 f.close()
 }}}

 If you can provide a failing test case, please reopen with more details.

-- 
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] #10364: Incorrect error message given when role does not have create database privilege

2009-03-17 Thread Django

#10364: Incorrect error message given when role does not have create database
privilege
---+
  Reporter:  tylere| Owner:  nobody
Status:  new   | Milestone:  1.1   
 Component:  GIS   |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * component:  Testing framework => GIS

Comment:

 This appears to only affect GIS databases, so I'm going to punt this to
 Justin's bailiwick. The fix seems fairly simple - we just need to print
 the exception obtained so that the user gets feedback on the underlying
 problem. The default creation backend
 
[http://code.djangoproject.com/browser/django/trunk/django/db/backends/creation.py?rev=10028#L361
 already does this], so it's just a matter of porting the logic to
 
[http://code.djangoproject.com/browser/django/trunk/django/contrib/gis/db/backend/postgis/creation.py?rev=%600028#L62
 somewhere near here]

-- 
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] #10521: Test failure of missing url '/' in test django.contrib.auth.tests.remote_user.py

2009-03-17 Thread Django

#10521: Test failure of missing url '/' in test
django.contrib.auth.tests.remote_user.py
-+--
  Reporter:  kegan   | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Authentication  |   Version:
Resolution:  invalid |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by ramiro):

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

Comment:

 You aren't supposed to run Django test suite tests using `manage.py`

 Closing as invalid because running `tests/runtests.py auth --verbosity=2`
 with an appropiate settings file shows the tests added in r10069 are run
 and don't generate error.

-- 
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] r10071 - django/trunk/tests/regressiontests/cache

2009-03-17 Thread noreply


Author: russellm
Date: 2009-03-17 05:40:04 -0500 (Tue, 17 Mar 2009)
New Revision: 10071

Modified:
   django/trunk/tests/regressiontests/cache/tests.py
Log:
Fixed #10517 -- Corrected cache name for file-based cache tests so that the 
filename can be valid under Windows. Thanks to Bob Thomas for the report and 
fix.

Modified: django/trunk/tests/regressiontests/cache/tests.py
===
--- django/trunk/tests/regressiontests/cache/tests.py   2009-03-17 10:30:17 UTC 
(rev 10070)
+++ django/trunk/tests/regressiontests/cache/tests.py   2009-03-17 10:40:04 UTC 
(rev 10071)
@@ -265,7 +265,7 @@
 """
 def setUp(self):
 self.dirname = tempfile.mkdtemp()
-self.cache = get_cache('file:///%s' % self.dirname)
+self.cache = get_cache('file://%s' % self.dirname)
 
 def tearDown(self):
 shutil.rmtree(self.dirname)


--~--~-~--~~~---~--~~
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] #10512: Ordering of non-model fields in a ModelForm, after #8164

2009-03-17 Thread Django

#10512: Ordering of non-model fields in a ModelForm, after #8164
---+
  Reporter:  mbi   | Owner:  Alex  
Status:  closed| Milestone:
 Component:  Forms |   Version:  SVN   
Resolution:  fixed |  Keywords:  modelform, field order
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 (In [10070]) Fixed #10512 -- Corrected the handling of extra fields on a
 ModelForm?. Thanks to Alex Gaynor for the 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
-~--~~~~--~~--~--~---

[Changeset] r10070 - in django/trunk: django/forms tests/modeltests/model_forms

2009-03-17 Thread noreply


Author: russellm
Date: 2009-03-17 05:30:17 -0500 (Tue, 17 Mar 2009)
New Revision: 10070

Modified:
   django/trunk/django/forms/models.py
   django/trunk/tests/modeltests/model_forms/models.py
Log:
Fixed #10512 -- Corrected the handling of extra fields on a ModelForm. Thanks 
to Alex Gaynor for the patch.

Modified: django/trunk/django/forms/models.py
===
--- django/trunk/django/forms/models.py 2009-03-16 20:54:57 UTC (rev 10069)
+++ django/trunk/django/forms/models.py 2009-03-17 10:30:17 UTC (rev 10070)
@@ -163,7 +163,7 @@
 field_list.append((f.name, formfield))
 field_dict = SortedDict(field_list)
 if fields:
-field_dict = SortedDict([(f, field_dict[f]) for f in fields if (not 
exclude) or (exclude and f not in exclude)])
+field_dict = SortedDict([(f, field_dict.get(f)) for f in fields if 
(not exclude) or (exclude and f not in exclude)])
 return field_dict
 
 class ModelFormOptions(object):

Modified: django/trunk/tests/modeltests/model_forms/models.py
===
--- django/trunk/tests/modeltests/model_forms/models.py 2009-03-16 20:54:57 UTC 
(rev 10069)
+++ django/trunk/tests/modeltests/model_forms/models.py 2009-03-17 10:30:17 UTC 
(rev 10070)
@@ -1450,6 +1450,19 @@
 >>> core.parent
 
 
+>>> class CategoryForm(ModelForm):
+... description = forms.CharField()
+... class Meta:
+... model = Category
+... fields = ['description', 'url']
+
+>>> CategoryForm.base_fields.keys()
+['description', 'url']
+
+>>> print CategoryForm()
+Description:
+The URL:
+
 # Clean up
 >>> import shutil
 >>> shutil.rmtree(temp_storage_dir)


--~--~-~--~~~---~--~~
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] #9239: Better reverse() handling for the (.*) pattern

2009-03-17 Thread Django

#9239: Better reverse() handling for the (.*) pattern
-+--
  Reporter:  mtredinnick | Owner:  mtredinnick
Status:  closed  | Milestone: 
 Component:  Core framework  |   Version:  1.0
Resolution:  wontfix |  Keywords: 
 Stage:  Unreviewed  | Has_patch:  0  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by mtredinnick):

  * status:  reopened => 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] #9239: Better reverse() handling for the (.*) pattern

2009-03-17 Thread Django

#9239: Better reverse() handling for the (.*) pattern
-+--
  Reporter:  mtredinnick | Owner:  mtredinnick
Status:  reopened| Milestone: 
 Component:  Core framework  |   Version:  1.0
Resolution:  |  Keywords: 
 Stage:  Unreviewed  | Has_patch:  0  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by mtredinnick):

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

Comment:

 Yes, it's still a 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] #9239: Better reverse() handling for the (.*) pattern

2009-03-17 Thread Django

#9239: Better reverse() handling for the (.*) pattern
-+--
  Reporter:  mtredinnick | Owner:  mtredinnick
Status:  closed  | Milestone: 
 Component:  Core framework  |   Version:  1.0
Resolution:  fixed   |  Keywords: 
 Stage:  Unreviewed  | Has_patch:  0  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Comment (by rdakin):

 Does that mean this should still be resolved ''wontfix''? The issue is
 still apparent in my testing.

-- 
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] #10515: Add rand and ror to QuerySet [PATCH]

2009-03-17 Thread Django

#10515: Add __rand__ and __ror__ to QuerySet [PATCH]
---+
  Reporter:  sebastian_noack   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Design decision needed| Has_patch:  1 
Needs_docs:  1 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Comment (by sebastian_noack):

 Maybe you guys are right, that there might be a better way to go. But if
 you look at EmptyQuerySet, there are hooks to handle it differently in
 QuerySet's ''__or__'' and ''__and__'' method. And sometimes there is a
 need to have similar logic when combining custom QuerySets, too. So it
 might be nice to have an API for modifying the behaviour of combining
 QuerySets. The ''__ror__''/''__rand__'' approach, was just the best idea I
 came up with, because this way the same problem is solved in Python
 itself. But maybe somebody else have a better idea.

-- 
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] #10512: Ordering of non-model fields in a ModelForm, after #8164

2009-03-17 Thread Django

#10512: Ordering of non-model fields in a ModelForm, after #8164
---+
  Reporter:  mbi   | Owner:  Alex  
Status:  new   | Milestone:
 Component:  Forms |   Version:  SVN   
Resolution:|  Keywords:  modelform, field order
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Comment (by mbi):

 Thank you Alex, your patch worked as expected here.

-- 
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] #10522: generic_inlineformset_factory's exclude option should accept tuples too

2009-03-17 Thread Django

#10522: generic_inlineformset_factory's exclude option should accept tuples too
--+-
 Reporter:  mk|   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Contrib apps  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 This is similar to #9171, which was fixed in [9086]

 from django.contrib.contenttypes.generic import
 generic_inlineformset_factory
 generic_inlineformset_factory(SomeModel, exclude=('somefield',)) causes an
 exception 'tuple has no attribute extend'

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

63 matches

Mail list logo