Re: [Django] #7931: Debug mode causes template includes to be parsed regardless of if tags

[Django]

#7931: Debug mode causes template includes to be parsed regardless of if tags
--+-
  Reporter:  hmur...@datalive.com.au  | Owner:  nobody  
   
Status:  closed   | Milestone:  
   
 Component:  Template system  |   Version:  SVN 
   
Resolution:  invalid  |  Keywords:  template debug 
include tags
 Stage:  Design decision needed   | Has_patch:  0   
   
Needs_docs:  0|   Needs_tests:  0   
   
Needs_better_patch:  0|  
--+-
Changes (by SmileyChris):

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

Comment:

 The change in behavior is reliant on `settings.TEMPLATE_DEBUG` (which
 usually is set to the same as `DEBUG`).

 There is no bug here: the template includes are parsed in both situations,
 the error is just swallowed silently if not in debug mode.

 As to whether the templates *should* always be parsed, we've got #12064 to
 talk about that now.

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

Re: [Django] #11526: LDAP authentication backend

[Django]

#11526: LDAP authentication backend
-+--
  Reporter:  psagers | Owner:  nobody
Status:  new | Milestone:
 Component:  Authentication  |   Version:  SVN   
Resolution:  |  Keywords:  ldap  
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by wogan):

 * cc: dja...@wogan.id.au (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] #12064: Impossible to conditionally include potentially non-existant templates

[Django]

#12064: Impossible to conditionally include potentially non-existant templates
--+-
  Reporter:  mkruisselbrink   | Owner:  nobody
Status:  new  | Milestone:
 Component:  Template system  |   Version:  1.1   
Resolution:   |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  1 
Needs_better_patch:  0|  
--+-
Comment (by SmileyChris):

 The proper fix, assuming this is deemed a valid bug, would be to remove
 `ConstantIncludeNode` altogether, not make it work near identically to
 `IncludeNode`.

-- 
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] #2507: [patch] LDAPBackend in django/contrib/auth/backends.py

[Django]

#2507: [patch] LDAPBackend in django/contrib/auth/backends.py
---+
  Reporter:  s...@mahonri5.net  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Contrib apps  |   Version:  SVN   
Resolution:|  Keywords:  ldap,usernames
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Changes (by wogan):

 * cc: dja...@wogan.id.au (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] #9356: CSRFMiddleware should take session key from request.session

[Django]

#9356: CSRFMiddleware should take session key from request.session
---+
  Reporter:  bthomas   | Owner:  nobody
Status:  closed| Milestone:  1.2   
 Component:  Contrib apps  |   Version:  1.0   
Resolution:  invalid   |  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Changes (by lukeplant):

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

Comment:

 !CsrfMiddleware no longer depends on the session, so this isn't valid any
 more.

-- 
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] r11665 - django/trunk/docs/ref

[noreply]

Author: lukeplant
Date: 2009-10-26 20:10:20 -0500 (Mon, 26 Oct 2009)
New Revision: 11665

Modified:
   django/trunk/docs/ref/settings.txt
Log:
Added 'version added' info to CSRF_* settings.



Modified: django/trunk/docs/ref/settings.txt
===
--- django/trunk/docs/ref/settings.txt  2009-10-27 00:49:33 UTC (rev 11664)
+++ django/trunk/docs/ref/settings.txt  2009-10-27 01:10:20 UTC (rev 11665)
@@ -148,6 +148,9 @@
 
 CSRF_COOKIE_NAME
 
+
+.. versionadded:: 1.2
+
 Default: ``'csrftoken'``
 
 The name of the cookie to use for the CSRF authentication token. This can be 
whatever you
@@ -158,6 +161,8 @@
 CSRF_COOKIE_DOMAIN
 --
 
+.. versionadded:: 1.2
+
 Default: ``None``
 
 The domain to be used when setting the CSRF cookie.  This can be useful for
@@ -171,6 +176,8 @@
 CSRF_FAILURE_VIEW
 -
 
+.. versionadded:: 1.2
+
 Default: ``'django.views.csrf.csrf_failure'``
 
 A dotted path to the view function to be used when an incoming request


--~--~-~--~~~---~--~~
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] r11664 - django/trunk/django/middleware

[noreply]

Author: lukeplant
Date: 2009-10-26 19:49:33 -0500 (Mon, 26 Oct 2009)
New Revision: 11664

Modified:
   django/trunk/django/middleware/csrf.py
Log:
Removed unused import.



Modified: django/trunk/django/middleware/csrf.py
===
--- django/trunk/django/middleware/csrf.py  2009-10-27 00:43:16 UTC (rev 
11663)
+++ django/trunk/django/middleware/csrf.py  2009-10-27 00:49:33 UTC (rev 
11664)
@@ -8,10 +8,6 @@
 import itertools
 import re
 import random
-try:
-from functools import wraps
-except ImportError:
-from django.utils.functional import wraps  # Python 2.3, 2.4 fallback.
 
 from django.conf import settings
 from django.core.urlresolvers import get_callable


--~--~-~--~~~---~--~~
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] r11663 - django/trunk/docs/ref/contrib

[noreply]

Author: lukeplant
Date: 2009-10-26 19:43:16 -0500 (Mon, 26 Oct 2009)
New Revision: 11663

Modified:
   django/trunk/docs/ref/contrib/csrf.txt
Log:
Use decorator syntax for csrf_exempt example.



Modified: django/trunk/docs/ref/contrib/csrf.txt
===
--- django/trunk/docs/ref/contrib/csrf.txt  2009-10-27 00:38:28 UTC (rev 
11662)
+++ django/trunk/docs/ref/contrib/csrf.txt  2009-10-27 00:43:16 UTC (rev 
11663)
@@ -212,9 +212,9 @@
 
 from django.views.decorators.csrf import csrf_exempt
 
+@csrf_exempt
 def my_view(request):
 return HttpResponse('Hello world')
-my_view = csrf_exempt(my_view)
 
 Like the middleware, the ``csrf_exempt`` decorator is composed of two parts: a
 ``csrf_view_exempt`` decorator and a ``csrf_response_exempt`` decorator, found


--~--~-~--~~~---~--~~
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] r11662 - django/branches/releases/1.1.X/docs/ref/contrib

[noreply]

Author: lukeplant
Date: 2009-10-26 19:38:28 -0500 (Mon, 26 Oct 2009)
New Revision: 11662

Modified:
   django/branches/releases/1.1.X/docs/ref/contrib/csrf.txt
Log:
[1.1.X] Fixed #10996 - documented login CSRF vulnerabilities in the 
CsrfMiddleware

1.1.X branch only fix - trunk is completely different now.



Modified: django/branches/releases/1.1.X/docs/ref/contrib/csrf.txt
===
--- django/branches/releases/1.1.X/docs/ref/contrib/csrf.txt2009-10-27 
00:36:34 UTC (rev 11661)
+++ django/branches/releases/1.1.X/docs/ref/contrib/csrf.txt2009-10-27 
00:38:28 UTC (rev 11662)
@@ -91,8 +91,8 @@
 CSRF attack with a GET request ought to be harmless.
 
 POST requests that are not accompanied by a session cookie are not protected,
-but they do not need to be protected, since the 'attacking' Web site
-could make these kind of requests anyway.
+but since these requests are not authenticated, they will usually be of limited
+risk.
 
 The Content-Type is checked before modifying the response, and only
 pages that are served as 'text/html' or 'application/xml+xhtml'
@@ -116,6 +116,12 @@
 a custom authentication system that manually sets cookies and the like,
 it won't help you.
 
+The middleware only partially protects against 'Login CSRF'.  If you have used
+standard Django views for logging in, then you will be protected, due to the 
way
+they work (the session must be established in the step before actually logging
+in, so the login step itself is protected).  If you have used a different way 
to
+log in, you may be vulnerable to Login CSRF.
+
 If your app creates HTML pages and forms in some unusual way, (e.g.
 it sends fragments of HTML in JavaScript document.write statements)
 you might bypass the filter that adds the hidden field to the form,


--~--~-~--~~~---~--~~
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] #5272: Password reset form resets passwords for all users sharing an email address

[Django]

#5272: Password reset form resets passwords for all users sharing an email 
address
---+
  Reporter:  Alper KANAT   | Owner:  
nobody 
Status:  closed| Milestone: 

 Component:  Contrib apps  |   Version:  
SVN
Resolution:  fixed |  Keywords:  
password reset form
 Stage:  Accepted  | Has_patch:  0  

Needs_docs:  0 |   Needs_tests:  0  

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

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

Comment:

 I don't understand why this needs to be fixed, now that #7723 has been
 fixed.  No passwords are reset until the link in the e-mail is clicked.
 If there is a complaint about the usability of the current system (e.g.
 the number of e-mails sent out etc, I can't remember exactly how it
 works), please file another bug.

 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] #9977: CSRFMiddleware needs template tag

[Django]

#9977: CSRFMiddleware needs template tag
-+--
  Reporter:  bthomas | Owner:  lukeplant
Status:  closed  | Milestone:  1.2  
 Component:  HTTP handling   |   Version:  SVN  
Resolution:  fixed   |  Keywords:  csrf 
 Stage:  Design decision needed  | Has_patch:  1
Needs_docs:  1   |   Needs_tests:  0
Needs_better_patch:  1   |  
-+--
Changes (by Alex):

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

Comment:

 Fixed in r11660.

-- 
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] #5272: Password reset form resets passwords for all users sharing an email address

[Django]

#5272: Password reset form resets passwords for all users sharing an email 
address
---+
  Reporter:  Alper KANAT   | Owner:  
nobody 
Status:  reopened  | Milestone: 

 Component:  Contrib apps  |   Version:  
SVN
Resolution:|  Keywords:  
password reset form
 Stage:  Accepted  | Has_patch:  0  

Needs_docs:  0 |   Needs_tests:  0  

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

 Given the stance in #7591 that email will not be enforced to be unique by
 default, this bug needs addressing.

-- 
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] #3512: Add "required" & "error" CSS classes to form rows in as_* methods

[Django]

#3512: Add "required" & "error" CSS classes to form rows in as_* methods
+---
  Reporter:  Waylan Limberg   | Owner:  nobody
Status:  reopened   | Milestone:
 Component:  Forms  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  1  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

 * cc: drack...@mac.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] #6646: included template blocks are not being overrided by parent template.

[Django]

#6646: included template blocks are not being overrided by parent template.
--+-
  Reporter:  anonymous| Owner:  walpatal   
Status:  new  | Milestone: 
 Component:  Template system  |   Version:  SVN
Resolution:   |  Keywords:  include, extends, block
 Stage:  Accepted | Has_patch:  1  
Needs_docs:  1|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Comment (by lukeplant):

 Replying to [comment:12 Thomas Steinacher ]:

 > The patch is working for me. Any reason this is not in trunk yet?

 Without docs for the point !SmileyChris mentioned it won't go in.  Also, I
 suspect that fixing #12064 would break this patch, because it effectively
 makes all include blocks 'dynamic' i.e. the actual template used is
 decided at render time, not compile time.  If my suspicions are correct,
 then there are definitely some design decisions to be made.

-- 
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] #12064: Impossible to conditionally include potentially non-existant templates

[Django]

#12064: Impossible to conditionally include potentially non-existant templates
--+-
  Reporter:  mkruisselbrink   | Owner:  nobody
Status:  new  | Milestone:
 Component:  Template system  |   Version:  1.1   
Resolution:   |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  1 
Needs_better_patch:  0|  
--+-
Changes (by lukeplant):

  * owner:  lukeplant => nobody
  * 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] #12092: grammatical error on http://docs.djangoproject.com/en/dev/intro/install/

[Django]

#12092: grammatical error on http://docs.djangoproject.com/en/dev/intro/install/
---+
 Reporter:  Abizern|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 The warning box near the end of the page starts with "If do either of the
 first two steps," I think this should be "If '''you''' do either…" (bold
 marks added word).

 I'm adding a shot of the relevant section:
 [http://emberapp.com/abizern/images/safari]

-- 
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] #12091: [PATCH] Support for WSGI applications within Django

[Django]

#12091: [PATCH] Support for WSGI applications within Django
+---
  Reporter:  Gustavo| Owner:  Gustavo
Status:  new| Milestone:  1.2
 Component:  HTTP handling  |   Version:  SVN
Resolution: |  Keywords:  WSGI   
 Stage:  Unreviewed | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by ubernostrum):

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

Comment:

 I think it'd be nice if this explained how it differs from the WSGI-
 oriented SoC branch, and indicated whether it builds on that work.

-- 
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] #6646: included template blocks are not being overrided by parent template.

[Django]

#6646: included template blocks are not being overrided by parent template.
--+-
  Reporter:  anonymous| Owner:  walpatal   
Status:  new  | Milestone: 
 Component:  Template system  |   Version:  SVN
Resolution:   |  Keywords:  include, extends, block
 Stage:  Accepted | Has_patch:  1  
Needs_docs:  1|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by Thomas Steinacher ):

 * cc: t...@eggdrop.ch (added)

Comment:

 The patch is working for me. Any reason this is not in trunk yet?

-- 
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] #12091: [PATCH] Support for WSGI applications within Django

[Django]

#12091: [PATCH] Support for WSGI applications within Django
---+
 Reporter:  Gustavo|   Owner:  Gustavo   
   Status:  new|   Milestone:  1.2   
Component:  HTTP handling  | Version:  SVN   
 Keywords:  WSGI   |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 With the attached patch, it will be possible to run WSGI applications from
 Django and even use such applications as Django views.

 It depends on the patch I supplied in #8927.

 Please let me know what you think about 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] #12090: Show admin actions on the edit pages too

[Django]

#12090: Show admin actions on the edit pages too
---+
  Reporter:  apollo13  | Owner:  nobody
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by carljm):

 * cc: carljm (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] #12090: Show admin actions on the edit pages too

[Django]

#12090: Show admin actions on the edit pages too
---+
  Reporter:  apollo13  | Owner:  nobody
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by jezdez):

 * cc: jezdez (added)
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 Interesting idea!

 One question though: The current admin actions usually return the user to
 the object list, what would be the behavior after running the action from
 the object detail page?

-- 
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] #12090: Show admin actions on the edit pages too

[Django]

#12090: Show admin actions on the edit pages too
--+-
 Reporter:  apollo13  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Currently the workflow for comment moderation might look like this
 (without knowing the comment moderation admin actions ;)):
  * Look at the overview page
  * If in doubt open the comment in a new page
  * if it's spam go back to the previous page, select it and execute the
 admin action

 We could redisplay the admin actions box in the detail views (where they
 of course would only effect the current object) to prevent the unneeded
 roundtrip.

-- 
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] #11010: Add a foundation for rowlevel permissions in Django

[Django]

#11010: Add a foundation for rowlevel permissions in Django
-+--
  Reporter:  apollo13| Owner:  apollo13
Status:  new | Milestone:  1.2 
 Component:  Authentication  |   Version:  SVN 
Resolution:  |  Keywords:  
 Stage:  Accepted| Has_patch:  1   
Needs_docs:  1   |   Needs_tests:  1   
Needs_better_patch:  1   |  
-+--
Changes (by apollo13):

  * owner:  nobody => apollo13

-- 
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] #11010: Add a foundation for rowlevel permissions in Django

[Django]

#11010: Add a foundation for rowlevel permissions in Django
-+--
  Reporter:  apollo13| Owner:  nobody
Status:  new | Milestone:  1.2   
 Component:  Authentication  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Comment (by apollo13):

 Replying to [comment:5 cont...@roelkramer.nl]:
 > I made my own row level permission system based on this patch. It's
 still in a very early stage, but if needed I can share my findings.
 Hi, I am working on this patch for 1.2 and it would be nice if you could
 share your backend; maybe we find something else to include or improve…

-- 
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] r11659 - in django/branches/releases/1.1.X: . docs/topics

[noreply]

Author: kmtracey
Date: 2009-10-26 10:31:47 -0500 (Mon, 26 Oct 2009)
New Revision: 11659

Modified:
   django/branches/releases/1.1.X/
   django/branches/releases/1.1.X/docs/topics/testing.txt
Log:
[1.1.X] Fixed #11961: Corrected a few typos in docs/testing.txt. Thanks to timo 
for the patch. 

Merge of r11599 from trunk.
Also updated svnmerge-integrated to reflect other changesets already backported,
and added a couple more that should not be merged to svnmerge-blocked.



Property changes on: django/branches/releases/1.1.X
___
Name: svnmerge-blocked
   - 
/django/trunk:11526,11586-11587,11590,11593-11595,11600,11618,11627,11636,11639-11641,11645-11647,11654
   + 
/django/trunk:11526,11586-11587,11590,11593-11595,11600,11618,11627,11636,11639-11642,11645-11647,11654-11655

Name: svnmerge-integrated
   - 
/django/trunk:1-11500,11523,11527-11528,11531-11552,11554,11577,11579-11581,11596,11623,11625,11634,11637,11648,11650,11652
   + 
/django/trunk:1-11500,11523,11527-11528,11531-11552,11554,11577,11579-11581,11588-11589,11591-11592,11596-11599,11601-11617,11619-11626,11628-11635,11637-11638,11643-11644,11648-11653,11656


Modified: django/branches/releases/1.1.X/docs/topics/testing.txt
===
--- django/branches/releases/1.1.X/docs/topics/testing.txt  2009-10-26 
15:15:17 UTC (rev 11658)
+++ django/branches/releases/1.1.X/docs/topics/testing.txt  2009-10-26 
15:31:47 UTC (rev 11659)
@@ -515,7 +515,7 @@
 >>> c = Client()
 >>> c.get('/customers/details/?name=fred=7')
 
-If you provide URL both an encoded GET data and a data argument,
+If you provide a URL with both an encoded GET data and a data argument,
 the data argument will take precedence.
 
 If you set ``follow`` to ``True`` the client will follow any redirects
@@ -627,7 +627,7 @@
 
 .. versionadded:: 1.1
 
-Makes an PUT request on the provided ``path`` and returns a
+Makes a PUT request on the provided ``path`` and returns a
 ``Response`` object. Useful for testing RESTful interfaces. Acts just
 like :meth:`Client.post` except with the PUT request method.
 
@@ -1127,11 +1127,11 @@
 
 During test running, each outgoing e-mail is saved in
 ``django.core.mail.outbox``. This is a simple list of all
-:class:`<~django.core.mail.EmailMessage>` instances that have been sent.
+:class:`~django.core.mail.EmailMessage` instances that have been sent.
 It does not exist under normal execution conditions, i.e., when you're not
 running unit tests. The outbox is created during test setup, along with the
-dummy :class:`<~django.core.mail.SMTPConnection>`. When the test framework is
-torn down, the standard :class:`<~django.core.mail.SMTPConnection>` class is
+dummy :class:`~django.core.mail.SMTPConnection`. When the test framework is
+torn down, the standard :class:`~django.core.mail.SMTPConnection` class is
 restored, and the test outbox is destroyed.
 
 The ``outbox`` attribute is a special attribute that is created *only* when


--~--~-~--~~~---~--~~
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] #12089: test client fails to collect sub-contexts

[Django]

#12089: test client fails to collect sub-contexts
+---
  Reporter:  akaihola   | Owner:  nobody
Status:  new| Milestone:
 Component:  Testing framework  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by akaihola):

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

Comment:

 The problem was that the same context object was appended to the
 `ContextList` over and over, and if I understand correctly, when the
 pushed contexts got popped, modified context was forgotten. At least
 `response.context` contained a list of multiple references to a single
 `RequestContext` object when I examined it with the debugger.

 The above patch makes deep copies of the `RequestContext` objects before
 adding them to the `ContextList` of the test client.

 Tests are included with the patch. The two template files shown as
 `/dev/null` by Trac (apparently it doesn't understand Git's diff format)
 are `/tests/templates/testclient/sub.html` and
 `/tests/templates/testclient/super.html`, respectively.

-- 
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] r11658 - django/branches/releases/1.1.X

[noreply]

Author: kmtracey
Date: 2009-10-26 10:15:17 -0500 (Mon, 26 Oct 2009)
New Revision: 11658

Modified:
   django/branches/releases/1.1.X/
Log:
[1.1.X] Block new features and fixes from svnmerge to 1.1.X branch.



Property changes on: django/branches/releases/1.1.X
___
Name: svnmerge-blocked
   - /django/trunk:11526
   + 
/django/trunk:11526,11586-11587,11590,11593-11595,11600,11618,11627,11636,11639-11641,11645-11647,11654


--~--~-~--~~~---~--~~
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] #12089: test client fails to collect sub-contexts

[Django]

#12089: test client fails to collect sub-contexts
---+
 Reporter:  akaihola   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Testing framework  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 If a main template renders a sub-template with a modified or newly created
 context, test client's `response.context` fails to include the modified
 context. An example using `{% with %}` and `{% include %}`:

 === main-template.html ===
 {{{
 {% with "some-value" as subvariable %}
   {% include sub-template.html %}
 {% endwith %}
 }}}

 === sub-template.html ===
 {{{
 The value of subvariable is "{{ subvariable }}".
 }}}

 If the test client requests a view which renders `main-template.html`, the
 variable `subvariable` can't be found in `response.context` as returned by
 `TestClient.get()`.

 The same happens if a custom template tag creates a new context and
 renders another template.

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

[Changeset] r11657 - in django/branches/releases/1.1.X: django/test tests/regressiontests/test_client_regress

[noreply]

Author: jacob
Date: 2009-10-26 10:04:32 -0500 (Mon, 26 Oct 2009)
New Revision: 11657

Modified:
   django/branches/releases/1.1.X/django/test/client.py
   
django/branches/releases/1.1.X/tests/regressiontests/test_client_regress/models.py
Log:
[1.1.X] Fixed #11371: Made `django.test.Client.put()` work for non-form-data 
PUT (i.e. JSON, etc.). Thanks, phyfus. Backport of [11656] from trunk.

Modified: django/branches/releases/1.1.X/django/test/client.py
===
--- django/branches/releases/1.1.X/django/test/client.py2009-10-26 
15:02:54 UTC (rev 11656)
+++ django/branches/releases/1.1.X/django/test/client.py2009-10-26 
15:04:32 UTC (rev 11657)
@@ -362,12 +362,18 @@
 else:
 post_data = data
 
+# Make `data` into a querystring only if it's not already a string. If
+# it is a string, we'll assume that the caller has already encoded it.
+query_string = None
+if not isinstance(data, basestring):
+query_string = urlencode(data, doseq=True)
+
 parsed = urlparse(path)
 r = {
 'CONTENT_LENGTH': len(post_data),
 'CONTENT_TYPE':   content_type,
 'PATH_INFO':  urllib.unquote(parsed[2]),
-'QUERY_STRING':   urlencode(data, doseq=True) or parsed[4],
+'QUERY_STRING':   query_string or parsed[4],
 'REQUEST_METHOD': 'PUT',
 'wsgi.input': FakePayload(post_data),
 }

Modified: 
django/branches/releases/1.1.X/tests/regressiontests/test_client_regress/models.py
===
--- 
django/branches/releases/1.1.X/tests/regressiontests/test_client_regress/models.py
  2009-10-26 15:02:54 UTC (rev 11656)
+++ 
django/branches/releases/1.1.X/tests/regressiontests/test_client_regress/models.py
  2009-10-26 15:04:32 UTC (rev 11657)
@@ -574,6 +574,23 @@
 self.assertEqual(response.status_code, 200)
 self.assertEqual(response.content, 'request method: DELETE')
 
+class RequestMethodStringDataTests(TestCase):
+def test_post(self):
+"Request a view with string data via request method POST"
+# Regression test for #11371
+data = u'{"test": "json"}'
+response = self.client.post('/test_client_regress/request_methods/', 
data=data, content_type='application/json')
+self.assertEqual(response.status_code, 200)
+self.assertEqual(response.content, 'request method: POST')
+
+def test_put(self):
+"Request a view with string data via request method PUT"
+# Regression test for #11371
+data = u'{"test": "json"}'
+response = self.client.put('/test_client_regress/request_methods/', 
data=data, content_type='application/json')
+self.assertEqual(response.status_code, 200)
+self.assertEqual(response.content, 'request method: PUT')
+
 class QueryStringTests(TestCase):
 def test_get_like_requests(self):
 for method_name in ('get','head','options','put','delete'):


--~--~-~--~~~---~--~~
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] r11656 - in django/trunk: django/test tests/regressiontests/test_client_regress

[noreply]

Author: jacob
Date: 2009-10-26 10:02:54 -0500 (Mon, 26 Oct 2009)
New Revision: 11656

Modified:
   django/trunk/django/test/client.py
   django/trunk/tests/regressiontests/test_client_regress/models.py
Log:
Fixed #11371: Made `django.test.Client.put()` work for non-form-data PUT (i.e. 
JSON, etc.). Thanks, phyfus.

Modified: django/trunk/django/test/client.py
===
--- django/trunk/django/test/client.py  2009-10-25 20:09:49 UTC (rev 11655)
+++ django/trunk/django/test/client.py  2009-10-26 15:02:54 UTC (rev 11656)
@@ -362,12 +362,18 @@
 else:
 post_data = data
 
+# Make `data` into a querystring only if it's not already a string. If
+# it is a string, we'll assume that the caller has already encoded it.
+query_string = None
+if not isinstance(data, basestring):
+query_string = urlencode(data, doseq=True)
+
 parsed = urlparse(path)
 r = {
 'CONTENT_LENGTH': len(post_data),
 'CONTENT_TYPE':   content_type,
 'PATH_INFO':  urllib.unquote(parsed[2]),
-'QUERY_STRING':   urlencode(data, doseq=True) or parsed[4],
+'QUERY_STRING':   query_string or parsed[4],
 'REQUEST_METHOD': 'PUT',
 'wsgi.input': FakePayload(post_data),
 }

Modified: django/trunk/tests/regressiontests/test_client_regress/models.py
===
--- django/trunk/tests/regressiontests/test_client_regress/models.py
2009-10-25 20:09:49 UTC (rev 11655)
+++ django/trunk/tests/regressiontests/test_client_regress/models.py
2009-10-26 15:02:54 UTC (rev 11656)
@@ -574,6 +574,23 @@
 self.assertEqual(response.status_code, 200)
 self.assertEqual(response.content, 'request method: DELETE')
 
+class RequestMethodStringDataTests(TestCase):
+def test_post(self):
+"Request a view with string data via request method POST"
+# Regression test for #11371
+data = u'{"test": "json"}'
+response = self.client.post('/test_client_regress/request_methods/', 
data=data, content_type='application/json')
+self.assertEqual(response.status_code, 200)
+self.assertEqual(response.content, 'request method: POST')
+
+def test_put(self):
+"Request a view with string data via request method PUT"
+# Regression test for #11371
+data = u'{"test": "json"}'
+response = self.client.put('/test_client_regress/request_methods/', 
data=data, content_type='application/json')
+self.assertEqual(response.status_code, 200)
+self.assertEqual(response.content, 'request method: PUT')
+
 class QueryStringTests(TestCase):
 def test_get_like_requests(self):
 for method_name in ('get','head','options','put','delete'):


--~--~-~--~~~---~--~~
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] #12088: Make the test Client class variable in TransactionTestCase

[Django]

#12088: Make the test Client class variable in TransactionTestCase
---+
 Reporter:  obeattie   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Testing framework  | Version:  1.1   
 Keywords:  test, client   |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 I have a subclass of Django's `TransactionTestCase`, and I would also like
 to be able to specify my own subclass of `Client` to use as the test's
 client. However, at the moment, this requires me to basically copy-and-
 paste all of the code out of the `TransactionTestCase`'s `__call__`
 method, as the `Client` class is hard-coded into that function. This also
 makes the use of `super` on the subclasses' `__call__` method impossible,
 as the `client` instance variable would just be reset to an instance of
 `Client` by `TransactionTestCase`.

 If it were made to be a class variable, subclasses could easily change
 this without having to override the `__call__` method. I've attached a
 diff proposal.

-- 
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] #399: Bigint field object needed

[Django]

#399: Bigint field object needed
---+
  Reporter:  jmad...@techie.com| Owner:  permon 
 
Status:  assigned  | Milestone:  1.2
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  
sprintsept14, bigint
 Stage:  Design decision needed| Has_patch:  1  
 
Needs_docs:  1 |   Needs_tests:  1  
 
Needs_better_patch:  1 |  
---+
Changes (by permon):

  * needs_docs:  0 => 1
  * needs_tests:  0 => 1

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

Re: [Django] #399: Bigint field object needed

[Django]

#399: Bigint field object needed
---+
  Reporter:  jmad...@techie.com| Owner:  permon 
 
Status:  assigned  | Milestone:  1.2
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  
sprintsept14, bigint
 Stage:  Design decision needed| Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  1 |  
---+
Comment (by permon):

 Patch updated to trunk. Because oldforms library is completely out, some
 changes are out. Needs testing in admin/newforms environment. Also some
 better documentation (look for all relevant places in docs) is needed.
 Patch is against r11655.

-- 
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] #12087: Django "TransactionTestCase" isn't

[Django]

#12087: Django "TransactionTestCase" isn't
---+
 Reporter:  brandon|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Testing framework  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 The Django TransactionTestCase fails to roll back the current database
 transaction at each test's conclusion, which can leave the current
 database connection in an unusable state and thus break test isolation.
 When Django is using PostgreSQL, and a test deliberately tries violating a
 database invariant (like inserting an illegal value, or a non-existent
 primary key) and receives a PostgreSQL runtime error, then all subsequent
 tests in that test class error out with the failure:

 {{{
 Traceback (most recent call last):
   File "/home/brandon/django/v/lib/python2.6/site-
 packages/Django-1.1.1-py2.6.egg/django/test/testcases.py", line 242, in
 __call__
 self._pre_setup()
   File "/home/brandon/django/v/lib/python2.6/site-
 packages/Django-1.1.1-py2.6.egg/django/test/testcases.py", line 217, in
 _pre_setup
 self._fixture_setup()
   File "/home/brandon/django/v/lib/python2.6/site-
 packages/Django-1.1.1-py2.6.egg/django/test/testcases.py", line 222, in
 _fixture_setup
 call_command('flush', verbosity=0, interactive=False)
   File "/home/brandon/django/v/lib/python2.6/site-
 packages/Django-1.1.1-py2.6.egg/django/core/management/__init__.py", line
 166, in call_command
 return klass.execute(*args, **defaults)
   File "/home/brandon/django/v/lib/python2.6/site-
 packages/Django-1.1.1-py2.6.egg/django/core/management/base.py", line 222,
 in execute
 output = self.handle(*args, **options)
   File "/home/brandon/django/v/lib/python2.6/site-
 packages/Django-1.1.1-py2.6.egg/django/core/management/base.py", line 351,
 in handle
 return self.handle_noargs(**options)
   File "/home/brandon/django/v/lib/python2.6/site-
 packages/Django-1.1.1-py2.6.egg/django/core/management/commands/flush.py",
 line 31, in handle_noargs
 sql_list = sql_flush(self.style, only_django=True)
   File "/home/brandon/django/v/lib/python2.6/site-
 packages/Django-1.1.1-py2.6.egg/django/core/management/sql.py", line 128,
 in sql_flush
 tables =
 connection.introspection.django_table_names(only_existing=True)
   File "/home/brandon/django/v/lib/python2.6/site-
 packages/Django-1.1.1-py2.6.egg/django/db/backends/__init__.py", line 510,
 in django_table_names
 tables = [t for t in tables if self.table_name_converter(t) in
 self.table_names()]
   File "/home/brandon/django/v/lib/python2.6/site-
 packages/Django-1.1.1-py2.6.egg/django/db/backends/__init__.py", line 491,
 in table_names
 return self.get_table_list(cursor)
   File "/home/brandon/django/v/lib/python2.6/site-
 
packages/Django-1.1.1-py2.6.egg/django/db/backends/postgresql/introspection.py",
 line 30, in get_table_list
 AND pg_catalog.pg_table_is_visible(c.oid)""")
 InternalError: current transaction is aborted, commands ignored until end
 of transaction block
 }}}

 The correction for this is very simple: the _fixture_teardown() method in
 django.test.testcases.TransactionTestCase needs its code changed from a
 do-nothing "pass" statement to something more effective:

 {{{
 def _fixture_teardown(self):
 transaction.rollback()
 }}}

 With this small change, test isolation is correctly achieved, and the rest
 of the test cases in the TransactionTestCase class can succeed and fail on
 their own rather than all dying with the error shown above.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #12086: Make QuerySet.delete() return the number of deleted objects

[Django]

#12086: Make QuerySet.delete() return the number of deleted objects
---+
  Reporter:  emulbreh  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  1 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

  * needs_better_patch:  => 0
  * has_patch:  0 => 1
  * needs_tests:  => 1
  * needs_docs:  => 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] #12086: Make QuerySet.delete() return the number of deleted objects

[Django]

#12086: Make QuerySet.delete() return the number of deleted objects
--+-
 Reporter:  emulbreh  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.1   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 This should be only be the number of objects deleted from the primary
 table (because other results may be hard to get with #7539).

-- 
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] #12085: Links to FKs in Admin (proposal)

[Django]

#12085: Links to FKs in Admin (proposal)
--+-
 Reporter:  Vlada Macek   |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 I frequently miss the admin ability to automatically link to change_forms
 of objects referenced by FKs:

 Currently when a !ForeignKey field is in list_display, the target's
 `__unicode__` is called and displayed in the cell. Why not to as well make
 it a link to the target's change_form provided it has !ModelAdmin
 registered and the user has the permissions?

 Can be controlled by some new attribute of !ModelAdmin, say
 ``foreign_key_links`` as the tuple of such fields.

 Yes, I can currently simulate that by creating a model method for each
 foreign key returning `` with `allow_tags=True` and replace the FK
 field in list_display, but these fields are second grade citizens:

  * cannot be ordered by
  * cannot be filtered upon
  * defining them is tedious
  * the quickiest dirty way is to hardcode the target URL to ``

 Sorry if it's duplicate or the feature is already in. Was unable to find
 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] #12075: Add wsgiorg.routing args support

[Django]

#12075: Add wsgiorg.routing args support
+---
  Reporter:  Gustavo| Owner:  Gustavo   
Status:  new| Milestone:  1.2   
 Component:  HTTP handling  |   Version:  SVN   
Resolution: |  Keywords:  WSGI, wsgiorg.routing_args
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Gustavo):

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

Comment:

 I forgot to mention, the patch assumes that the WSGI environment is
 available, which won't true with mod_python until the patch I sent for
 #8927 is applied.

-- 
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] #12084: Document the return type of QuerySet.update()

[Django]

#12084: Document the return type of QuerySet.update()
---+
 Reporter:  anonymous  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 [http://docs.djangoproject.com/en/dev/topics/db/queries/#updating-
 multiple-objects-at-once From the documentation]: "The update() method is
 applied instantly and doesn't return anything […]"

 This is not true. `QuerySet.update()` returns the number of rows affected
 by the `UPDATE` query, which is quite useful. The
 
[http://code.djangoproject.com/browser/django/trunk/tests/modeltests/update/models.py
 update tests] rely on this feature. Make it part of the public API.

-- 
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] #12083: technical_404_response should handle KeyError because 'tried' key might be not present

[Django]

#12083: technical_404_response should handle KeyError because 'tried' key might 
be
not present
-+--
  Reporter:  pigletto| Owner:  nobody
Status:  reopened| Milestone:
 Component:  Core framework  |   Version:  1.1   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by pigletto):

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

Comment:

 I've attached diff file with test case and patch included.

 Failing test gives output like:

 {{{
 ERROR: test_404 (regressiontests.views.tests.debug.DebugViewTests)
 --
 Traceback (most recent call last):
   File
 "/home/svnSandbox/django_dev/tests/regressiontests/views/tests/debug.py",
 line 24, in test_404
 response = self.client.get('/views/raises404/')
   File "/home/svnSandbox/django_dev/django/test/client.py", line 281, in
 get
 response = self.request(**r)
   File "/home/svnSandbox/django_dev/django/core/handlers/base.py", line
 92, in get_response
 response = callback(request, *callback_args, **callback_kwargs)
   File "/home/svnSandbox/django_dev/tests/regressiontests/views/views.py",
 line 46, in raises404
 return technical_404_response(request, e)
   File "/home/svnSandbox/django_dev/django/views/debug.py", line 247, in
 technical_404_response
 tried = exception.args[0]['tried']
 KeyError: 'tried'
 }}}

 The problem may appear only when '''request.path_info''' doesn't match
 regex r'^/' defined for RegexURLResolver (urlresolvers.py):
 {{{
 def get_resolver(urlconf):
 if urlconf is None:
 from django.conf import settings
 urlconf = settings.ROOT_URLCONF
 return RegexURLResolver(r'^/', urlconf)

 (...)

 class RegexURLResolver(object):
 def __init__(self, regex, urlconf_name, default_kwargs=None,
 app_name=None, namespace=None):
 # regex is a string representing a regular expression.
 # urlconf_name is a string representing the module containing
 URLconfs.
 self.regex = re.compile(regex, re.UNICODE)
 (...)

 def resolve(self, path):
 tried = []
 match = self.regex.search(path)
 if match:
 (...)
 raise Resolver404, {'tried': tried, 'path': new_path}
 raise Resolver404, {'path' : path}
 }}}

 I've found this issue when doing some (possibly dirty) hacking on
 ''request.path_info'' in my middleware class.
 Otherwise it seems to be not possible to raise this exception as both
 WSGIRequest and !ModPythonRequest are forcing ''request.path_info'' to be
 '/' instead of empty string. However, RegexURLResolver.resolve reflects
 this situation so provided patch might be desirable.

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