Re: [Django] #16676: The 'add' filter should stringify value or argument if the other value is a string

[Django]

#16676: The 'add' filter should stringify value or argument if the other value 
is a
string
-+-
 Reporter:  dtrebbien|Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.3
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by loewis):

 In [16950]:
 {{{
 #!CommitTicketReference repository="" revision="16950"
 Merged revisions
 
16743,16745,16747-16750,16752-16754,16756-16760,16770,16773-16800,16802-16804,16806,16808,16811,16813,16815,16817-16826,16829-16833,16835-16836,16838-16843,16845-16858,16860-16866,16868,16871-16877,16882-16890,16893-16947
 via svnmerge from
 https://code.djangoproject.com/svn/django/trunk

 
   r16743 | gabrielhurley | 2011-09-09 23:36:58 +0200 (Fr, 09 Sep 2011) | 2
 lines

   Fixed #16791 -- Updated a broken URL in the README file. Thanks to
 paulcwatts for the report and patch.
 
   r16745 | Alex | 2011-09-09 23:45:58 +0200 (Fr, 09 Sep 2011) | 1 line

   Switch to using explicit new-style division behavior, rather than
 relying on teh classic behavior.
 
   r16747 | SmileyChris | 2011-09-10 00:32:38 +0200 (Sa, 10 Sep 2011) | 1
 line

   Fix and test for cleaning a non-string value in a URLField
 
   r16748 | gabrielhurley | 2011-09-10 00:33:28 +0200 (Sa, 10 Sep 2011) | 2
 lines

   Fixed #16786 -- Minor cleanups in the memcached section of the caching
 topic guide. Thanks to jamesp for the report and patch.
 
   r16749 | jbronn | 2011-09-10 00:34:23 +0200 (Sa, 10 Sep 2011) | 1 line

   Fixed #16408 -- Fixed conversion of dates, and other problems with the
 SpatiaLite backend.
 
   r16750 | jbronn | 2011-09-10 00:47:18 +0200 (Sa, 10 Sep 2011) | 1 line

   Removed extra call to `syncdb` that slipped in with r16749.
 
   r16752 | SmileyChris | 2011-09-10 00:57:12 +0200 (Sa, 10 Sep 2011) | 1
 line

   Fixes #16664 -- URLField's to_python method fails with ValueError on
 some urls on python 2.7. Based on patch by zigzag.
 
   r16753 | russellm | 2011-09-10 01:02:33 +0200 (Sa, 10 Sep 2011) | 1 line

   Added two pointless query repeats to work around a known issue with
 MySQL that was causing failures in our test suite.
 
   r16754 | gabrielhurley | 2011-09-10 01:25:48 +0200 (Sa, 10 Sep 2011) | 2
 lines

   Fixed #16782 -- Corrected a broken cross-reference to the database
 engine setting in the tutorial. Thanks to mjumbewu for the report and
 patch.
 
   r16756 | kmtracey | 2011-09-10 02:05:48 +0200 (Sa, 10 Sep 2011) | 2
 lines

   Fixed #15722: ensure formsets evaluate to True even if they have no
 forms. Thanks mlavin.
 
   r16757 | jbronn | 2011-09-10 02:29:34 +0200 (Sa, 10 Sep 2011) | 1 line

   Fixed #13670 -- Comparisons with the spatial adapter won't blow up in
 some corner cases.  Thanks, milosu for the bug report and jpaulett for the
 patch.
 
   r16758 | russellm | 2011-09-10 02:46:38 +0200 (Sa, 10 Sep 2011) | 1 line

   Added protection against spoofing of X_FORWARDED_HOST headers. A
 security announcement will be made shortly.
 
   r16759 | russellm | 2011-09-10 02:46:48 +0200 (Sa, 10 Sep 2011) | 1 line

   Corrected an issue which could allow attackers to manipulate session
 data using the cache. A security announcement will be made shortly.
 
   r16760 | russellm | 2011-09-10 02:47:00 +0200 (Sa, 10 Sep 2011) | 1 line

   Altered the behavior of URLField to avoid a potential DOS vector, and to
 avoid potential leakage of local filesystem data. A security announcement
 will be made shortly.
 
   r16770 | Alex | 2011-09-10 03:53:56 +0200 (Sa, 10 Sep 2011) | 1 line

   Make ``Formset.__getitem__`` O(1), rather than O(n).  If you override
 ``__iter__`` you now need to also override ``__getitem__`` for consistant
 behavior.  Thanks to Carl and Russ for the review.
 
   r16773 | Alex | 2011-09-10 04:42:05 +0200 (Sa, 10 Sep 2011) | 1 line

   Fixed #11404.  Added ``FormSet.has_changed``, for consistancy with
 ``Form.has_changed``. Thanks to michelts for the patch.
 
   r16774 | Alex | 2011-09-10 04:52:37 +0200 (Sa, 10 Sep 2011) | 1 line

   Fixed #16793. Added more cross referencing to the load tag's
 documentation.  Thanks to bluejeansummer for the patch.
 
   r16775 | jbronn | 2011-09-10 05:04:30 +0200 (Sa, 10 Sep 2011) | 1 line

   Fixed #16790 -- Modified the geographic admin to work after 

Re: [Django] #16676: The 'add' filter should stringify value or argument if the other value is a string

[Django]

#16676: The 'add' filter should stringify value or argument if the other value 
is a
string
-+-
   Reporter:  dtrebbien  |  Owner:  aaugustin
   Type:  Bug| Status:  closed
  Milestone: |  Component:  Template system
Version:  1.3|   Severity:  Normal
 Resolution:  fixed  |   Keywords:
   Triage Stage:  Ready for  |  Has patch:  1
  checkin|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by julien):

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


Comment:

 In [16851]:
 {{{
 #!CommitTicketReference repository="" revision="16851"
 Fixed #16676 -- Corrected the behavior of the 'add' template filter to
 return an empty string instead of the given value unchanged in the case of
 an invalid use. Thanks to dtrebbien for the report and to Aymeric Augustin
 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.

Re: [Django] #16676: The 'add' filter should stringify value or argument if the other value is a string

[Django]

#16676: The 'add' filter should stringify value or argument if the other value 
is a
string
-+-
   Reporter:  dtrebbien  |  Owner:  aaugustin
   Type:  Bug| Status:  new
  Milestone: |  Component:  Template system
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Ready for  |  Has patch:  1
  checkin|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-

Comment (by jacob):

 No, `TEMPLATE_STRING_IF_INVALID` is for variables; there's no precedent in
 using it for filters, and I don't think we should expand it at all. It
 already causes enough problems!

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

-- 
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] #16676: The 'add' filter should stringify value or argument if the other value is a string

[Django]

#16676: The 'add' filter should stringify value or argument if the other value 
is a
string
-+-
   Reporter:  dtrebbien  |  Owner:  aaugustin
   Type:  Bug| Status:  new
  Milestone: |  Component:  Template system
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Ready for  |  Has patch:  1
  checkin|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-

Comment (by julien):

 Question: should `settings.TEMPLATE_STRING_IF_INVALID` be returned instead
 of a systematic hardcoded empty string, or should that setting be reserved
 for invalid variables?

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

-- 
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] #16676: The 'add' filter should stringify value or argument if the other value is a string

[Django]

#16676: The 'add' filter should stringify value or argument if the other value 
is a
string
-+-
   Reporter:  dtrebbien  |  Owner:  aaugustin
   Type:  Bug| Status:  new
  Milestone: |  Component:  Template system
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Ready for  |  Has patch:  1
  checkin|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by aaugustin):

 * stage:  Accepted => Ready for checkin


Comment:

 The initial patch was reviewed and marked as RFC by Russell. Since you
 just confirmed that the solution it uses is correct, I'm marking this
 ticket as RFC again (even though I'm the author).

 The patch that must be committed is the first one, "16676.patch".

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

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

Re: [Django] #16676: The 'add' filter should stringify value or argument if the other value is a string

[Django]

#16676: The 'add' filter should stringify value or argument if the other value 
is a
string
-+-
   Reporter:  dtrebbien  |  Owner:  aaugustin
   Type:  Bug| Status:  new
  Milestone: |  Component:  Template system
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
Changes (by jacob):

 * stage:  Design decision needed => Accepted


Comment:

 The fix here is to change the template to return the empty string as the
 documentation says. Returning the left-hand-side on a failure is weird.
 The auto-stringifying-behavior suggested doesn't sound like it matches
 Django very wel, so let's not do 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] #16676: The 'add' filter should stringify value or argument if the other value is a string

[Django]

#16676: The 'add' filter should stringify value or argument if the other value 
is a
string
-+-
   Reporter:  dtrebbien  |  Owner:  aaugustin
   Type:  Bug| Status:  new
  Milestone: |  Component:  Template system
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Design |  Has patch:  1
  decision needed|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-

Comment (by julien):

 An approach would be to return `settings.TEMPLATE_STRING_IF_INVALID`
 (which defaults to an empty string). However, I'd be happy enough with the
 doc being modified to reflect the current behaviour.

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

-- 
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] #16676: The 'add' filter should stringify value or argument if the other value is a string

[Django]

#16676: The 'add' filter should stringify value or argument if the other value 
is a
string
-+-
   Reporter:  dtrebbien  |  Owner:  aaugustin
   Type:  Bug| Status:  new
  Milestone: |  Component:  Template system
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Design |  Has patch:  1
  decision needed|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by aaugustin):

 * owner:  nobody => aaugustin


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

-- 
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] #16676: The 'add' filter should stringify value or argument if the other value is a string

[Django]

#16676: The 'add' filter should stringify value or argument if the other value 
is a
string
-+-
   Reporter:  dtrebbien  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Template system
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Design |  Has patch:  1
  decision needed|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-

Comment (by dtrebbien):

 I prefer Aymeric's first patch. Preserving backward compatibility with
 behavior that contradicts the docs does not seem preferable to making the
 behavior conform to current wording. Also, I think that returning an empty
 string is more consistent with the template system's tendency to return
 nothing if there was an error (e.g.: attempting to print an undefined
 variable).

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

-- 
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] #16676: The 'add' filter should stringify value or argument if the other value is a string

[Django]

#16676: The 'add' filter should stringify value or argument if the other value 
is a
string
-+-
   Reporter:  dtrebbien  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Template system
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Design |  Has patch:  1
  decision needed|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-

Comment (by aaugustin):

 In theory, I find it slightly better to display nothing that to display a
 wrong result. For instance, if someone adds total price and shipping cost
 with this filter (an horrible idea for sure, and a strong argument against
 the existence of the `add` filter), and accidentally has one of these
 values represented as a string, the resulting price would be wrong.

 In practice, I understand the value of preserving backwards compatibility.

 I'm attaching an alternative patch that changes the docs to match the
 code. I'm still slightly in favor of the initial patch. But what really
 matters is to resolve the inconsistency between the code and the docs, one
 way or another.

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

-- 
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] #16676: The 'add' filter should stringify value or argument if the other value is a string

[Django]

#16676: The 'add' filter should stringify value or argument if the other value 
is a
string
-+-
   Reporter:  dtrebbien  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Template system
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Design |  Has patch:  1
  decision needed|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by SmileyChris):

 * stage:  Ready for checkin => Design decision needed


Comment:

 Although the documentation has stated (for quite some time) that it
 returns an empty string, the current behavior of returning the original
 input is an acceptable response to an error. The docs say:

 > In case of error, they should return either the original input or an
 empty string -- whichever makes more sense.

 There could be minor elements of backwards incompatibility if we change
 this. Perhaps just changing the docs to match the behavior would be
 alright to do 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] #16676: The 'add' filter should stringify value or argument if the other value is a string

[Django]

#16676: The 'add' filter should stringify value or argument if the other value 
is a
string
-+-
   Reporter:  dtrebbien  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Template system
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Ready for  |  Has patch:  1
  checkin|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by russellm):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #16676: The 'add' filter should stringify value or argument if the other value is a string

[Django]

#16676: The 'add' filter should stringify value or argument if the other value 
is a
string
-+-
   Reporter:  dtrebbien  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Template system
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
Changes (by aaugustin):

 * has_patch:  0 => 1


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

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

Re: [Django] #16676: The 'add' filter should stringify value or argument if the other value is a string

[Django]

#16676: The 'add' filter should stringify value or argument if the other value 
is a
string
-+-
   Reporter:  dtrebbien  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Template system
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
Changes (by aaugustin):

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


Comment:

 In Python it's an error to add a string and an int:
 {{{
 >>> 'a' + 1
 Traceback (most recent call last):
   File "", line 1, in 
 TypeError: cannot concatenate 'str' and 'int' objects
 >>> 1 + 'a'
 Traceback (most recent call last):
   File "", line 1, in 
 TypeError: unsupported operand type(s) for +: 'int' and 'str'
 }}}

 In this case, the proper output is an empty string, as the docs says. I
 could confirm that Django returns the first value. It's a bug.

 

 However, `|add` doesn't really make sense with strings. `+` on strings is
 just concatenation, and concatenation is natively provided by the template
 engine.

 Instead of `{{ strval|add:intval }}`, just write `{{ strval }}{{ intval
 }}`.

 For this reason, I don't like the idea of converting both values to
 strings.

 

 I'm attaching a patch with tests (actually, the tests existed, but they
 contradicted the documentation; I think the documentation has precedence).
 I also fixed a naked except -- we never want to catch !BaseException.

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

-- 
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] #16676: The 'add' filter should stringify value or argument if the other value is a string

[Django]

#16676: The 'add' filter should stringify value or argument if the other value 
is a
string
---+-
 Reporter:  dtrebbien  |  Owner:  nobody
 Type:  Bug| Status:  new
Milestone: |  Component:  Template system
  Version:  1.3|   Severity:  Normal
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
UI/UX:  0  |
---+-
 The 1.3 documentation for the `add` filter states:

 > This filter will first try to coerce both values to integers. If this
 fails, it'll attempt to add the values together anyway. This will work on
 some data types (strings, list, etc.) and fail on others. If it fails, the
 result will be an empty string.

 When the value and argument represent the second case ("If this fails,
 it'll attempt to add the values together anyway.") and one is a string
 while the other is a number, the result of the `add` filter is simply the
 value.

 Similar to the fix for ticket #393, I think that for this second case and
 if either value or argument to the filter is a string, the other value
 should be stringified.

 === Test cases ===

 {{{
 {{ 'test'|add:2 }}
 }}}

 Result is: `test` \\
 Expected result: `test2`

 {{{
 {{ 2|add:'test' }}
 }}}

 Result is: `2` \\
 Expected result: `2test`

 === Workarounds ===
 For the first test case, one workaround is to use a `{% with %}` tag:

 {{{
 {% with 2|stringformat:'d' as arg_as_str %}
 {{ 'test'|add:arg_as_str }}
 {% endwith %}
 }}}

 For the second test case, the `stringformat` filter can be used to convert
 the number to a string before `add` is applied:
 {{{
 {{ 2|stringformat:'d'|add:'test' }}
 }}}

 === Related tickets ===
 * Ticket #393 [patch] Filters don't take the str() value of a var
 * Ticket #8088 Template system improvement: "cat" filter, "include" tag
 with filters
 * Ticket #11687 The 'add' template filter only works for integers, and can
 fail noisily

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

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