Re: [Django] #7048: Support clearing FileFields with ModelForms

[Django]

#7048: Support clearing FileFields with ModelForms
---+
  Reporter:  jarrow| Owner:  brosner
Status:  assigned  | Milestone:  1.2
 Component:  django.contrib.admin  |   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  1  
Needs_better_patch:  0 |  
---+
Changes (by DrMeers):

 * cc: drme...@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] #2912: django.contrib.syndication.feeds.py:Feed store the HttpRequest so it can be accessed

[Django]

#2912: django.contrib.syndication.feeds.py:Feed store the HttpRequest so it can 
be
accessed
-+--
  Reporter:  freyt...@handhelds.org  | Owner:  nobody
Status:  closed  | Milestone:
 Component:  RSS framework   |   Version:
Resolution:  fixed   |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by dc):

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

Comment:

 Fixed in [5654]

-- 
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] #9212: German Umlauts and possible other foreign languages special characters

[Django]

#9212: German Umlauts and possible other foreign languages special characters
---+
  Reporter:  nekron| Owner:  nobody 
Status:  reopened  | Milestone: 
 Component:  Internationalization  |   Version:  1.1
Resolution:|  Keywords:  Umlauts
 Stage:  Accepted  | Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Comment (by kmtracey):

 Replying to [comment:14 thie1210]:

 Why are you using version 0.14.1?  The easiest fix would be to update to a
 more recent level.  At the time this change went in it was hard to find
 precompiled binaries for Windows higher than 0.13.  Since then a source
 has been found (see http://docs.djangoproject.com/en/dev/topics/i18n
 /#gettext-on-windows) so there is less motivation to workaround gettext
 problems in Django code.

 What you seem to be reporting is that the version 0.14.1 you have respects
 the `--from-code` for .py files, which the versions I found that exhibited
 the original problem did not do.  The 0.13.1 likely used by the original
 reporter did not, nor did some other 0.14.4 Windows binaries I found.
 These would both re-encode the input file to utf-8 assuming an input
 encoding of iso-8859-1 (not ASCII).  Based on the error you are getting,
 the version you have is not doing this, so our attempt to un-do it fails.

 That leaves us with being unable to figure out, based on reported version,
 whether the command we are calling mangles its input. If we cannot figure
 that out, we cannot know whether un-do the mangling.  Given we've now
 updated our docs to include pointers to how to get a level of gettext
 utilities for Windows that does not exhibit the original problem, my
 initial inclination for how to fix this new problem is to remove the fix
 we put in for the original problem, and add a requirement that you must
 use gettext 0.15 or higher.

-- 
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] #6992: Better error message if Middleware.process_response returns None

[Django]

#6992: Better error message if Middleware.process_response returns None
-+--
  Reporter:  guettli | Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  1   |  
-+--
Changes (by SmileyChris):

  * needs_better_patch:  0 => 1

Comment:

 Error message is a wee bit confusing (and is the wsgi handler isn't the
 only place where this is needed - maybe a small refactor would be good).

-- 
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] #6675: Better error message if cleaned_data is missing (unbound Form)

[Django]

#6675: Better error message if cleaned_data is missing (unbound Form)
---+
  Reporter:  guettli   | Owner:  nobody
Status:  closed| Milestone:
 Component:  Forms |   Version:  SVN   
Resolution:  wontfix   |  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by SmileyChris):

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

Comment:

 That message is even more confusing, since we're talking about a Form not
 a Field.

 Also, this patch is stopping attribute access to forms, which is
 completely backwards incompatible.

-- 
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] #6749: Generic week view displays Sunday objects in both the current and next week

[Django]

#6749: Generic week view displays Sunday objects in both the current and next 
week
+---
  Reporter:  garrison   | Owner:  nobody  
Status:  new| Milestone:  
 Component:  Generic views  |   Version:  SVN 
Resolution: |  Keywords:  archive_week
 Stage:  Accepted   | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  1   
Needs_better_patch:  0  |  
+---
Changes (by SmileyChris):

  * 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] #7005: add orphans support for object_list pagination

[Django]

#7005: add orphans support for object_list pagination
-+--
  Reporter:  shadfc  | Owner:  shadfc   

Status:  assigned| Milestone:   

 Component:  Generic views   |   Version:  SVN  

Resolution:  |  Keywords:  orphans 
object_list paginator
 Stage:  Design decision needed  | Has_patch:  1

Needs_docs:  0   |   Needs_tests:  1

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

  * needs_tests:  0 => 1
  * stage:  Accepted => Design decision needed

Comment:

 If you feel passionate about it, feel free to bring it up in the django-
 dev google group.

 A quick review says this looks near ready for checkin if it is considered
 worthy. My only point would be that for full backwards compatibility, the
 new argument should be added to the end of the generic view definition.
 And yeah, no current tests isn't a good excuse ;)

 As an aside, the docs in the patch regarding Paginator orphans are good
 and should be committed either way. If someone was motivated to separate
 this to a different ticket, that would be good.

-- 
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] #6766: TEMPLATE_STRING_IF_INVALID should work for loops

[Django]

#6766: TEMPLATE_STRING_IF_INVALID should work for loops
-+--
  Reporter:  guettli | Owner:  nobody
Status:  new | Milestone:
 Component:  Template system |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by SmileyChris):

  * stage:  Accepted => Design decision needed

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

Re: [Django] #6580: Default argument to `getlist` on QueryDict

[Django]

#6580: Default argument to `getlist` on QueryDict
+---
  Reporter:  dcramer| Owner:  nobody
Status:  new| Milestone:
 Component:  HTTP handling  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  1  |  
+---
Changes (by SmileyChris):

  * needs_better_patch:  0 => 1

Comment:

 Patch looks good. The `getlist` docstring should be updated too though.

-- 
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] #6273: Support for passwd-like password changing

[Django]

#6273: Support for passwd-like password changing
--+-
  Reporter:  toxik| Owner:  justinlilly
Status:  new  | Milestone: 
 Component:  django-admin.py  |   Version:  SVN
Resolution:   |  Keywords: 
 Stage:  Accepted | Has_patch:  1  
Needs_docs:  0|   Needs_tests:  1  
Needs_better_patch:  0|  
--+-
Changes (by SmileyChris):

  * needs_tests:  0 => 1

Comment:

 It's not that complicated: monkeypatch the `_get_pass` method in your
 tests to return what you want without prompting.

-- 
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] #9212: German Umlauts and possible other foreign languages special characters

[Django]

#9212: German Umlauts and possible other foreign languages special characters
---+
  Reporter:  nekron| Owner:  nobody 
Status:  reopened  | Milestone: 
 Component:  Internationalization  |   Version:  1.1
Resolution:|  Keywords:  Umlauts
 Stage:  Accepted  | Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by thie1210):

  * status:  closed => reopened
  * version:  SVN => 1.1
  * resolution:  fixed =>

Comment:

 Hi guys,

 I'm running xgettext version 0.14.1 here. The makemessages command was
 working fine until I updated from v1.0 to v1.1. I now get the following
 error:

 {{{
 File "/usr/lib/python2.3/site-
 packages/django/core/management/commands/makemessages.py", line 166, in
 make_messages msgs = msgs.decode('utf-8').encode('iso-8859-1')
 UnicodeEncodeError: 'latin-1' codec can't encode character u'\u2009' in
 position 600: ordinal not in range(256)
 }}}


 The file in questions, views.py, contains unicode strings and characters
 (u2009, the thin space for instance),

 It's true that version 0.14.1 of xgettext assume ASCII input files for
 input. However, you can specify the encoding of the input files with the
 "--from-code" option. And that's what's done in makemessages.py when
 xgettext gets used at line 128.

 I've bypassed the xgettext_reencodes_utf8 test in my makemessages.py file
 and I'm now back up and running. I'm new to this so I don't know how to
 make an official change. I guess we need a new solution for the original
 issue 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
-~--~~~~--~~--~--~---

[Django] #11884: Clarify in documentation how to enable built-in reference in admin.

[Django]

#11884: Clarify in documentation how to enable built-in reference in admin.
---+
 Reporter:  DmitryRisenberg|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.1   
 Keywords:  admin reference setup  |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 Setting up [http://docs.djangoproject.com/en/dev/topics/templates/#using-
 the-built-in-reference built-in reference in admin] is not described
 anywhere in the docs - it requires adding
 {{{django.contrib.admindocs.urls}}} to {{{INSTALLED_APPS}}}, adding
 {{{(r'^admin/doc/', include('django.contrib.admindocs.urls'))}}} to
 {{{urlpatterns}}} and installing docutils if they are not present. Finding
 this out for me was untrivial and required googling, so I would add
 description of these steps to the corresponding section of documentation
 (see 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
-~--~~~~--~~--~--~---

[Django] #11883: Docs should really point out that you can set template_name of a flatpage in the admin

[Django]

#11883: Docs should really point out that you can set template_name of a 
flatpage
in the admin
--+-
 Reporter:  Svenstaro |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Documentation | Version:  1.0   
 Keywords:  flatpage admin template_name  |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Just as the title says. I just spent 2h hunting for how to set a
 flatpage#s template_name when I should merely have looked in the admin
 under advanced options. Please add it and make it easier for other users
 who can't spend so much time to look for 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
-~--~~~~--~~--~--~---

[Django] #11882: Documentation missing for django.contrib.admin.ModelAdmin.formfield_for_manytomany

[Django]

#11882: Documentation missing for
django.contrib.admin.ModelAdmin.formfield_for_manytomany
-+--
 Reporter:  Nils L   |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Documentation| Version:  1.1   
 Keywords:  formfield_for_manytomany, admin  |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 The documentation only describes the formfield_for_foreignkey method, but
 not the formfield_for_manytomany method of ModelAdmin.

 See
 
[/en/dev/ref/contrib/admin/#django.contrib.admin.ModelAdmin.formfield_for_foreignkey].
 It would be good with some mention of the formfield_for_manytomany method
 there.

-- 
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] #2016: [patch] Decorator for template tags that load objects

[Django]

#2016: [patch] Decorator for template tags that load objects
+---
  Reporter:  ja...@pengale.com  | Owner:  nobody
Status:  assigned   | Milestone:
 Component:  Template system|   Version:
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  1  |   Needs_tests:  1 
Needs_better_patch:  1  |  
+---
Comment (by marcusf):

 Sorry for the inconvenience, I've attached the new combined 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] #11878: Allow using a settings.py setting instead of runserver's "--adminmedia" settings

[Django]

#11878: Allow using a settings.py setting instead of runserver's  "--adminmedia"
settings
+---
  Reporter:  ab...@hal.elte.hu  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution:  wontfix|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by kmtracey):

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

Comment:

 In the ticket which led to the implementation of `--adminmedia` (#2600) a
 setting was specifically rejected in favor of the runserver option.

-- 
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] #2016: [patch] Decorator for template tags that load objects

[Django]

#2016: [patch] Decorator for template tags that load objects
+---
  Reporter:  ja...@pengale.com  | Owner:  nobody
Status:  assigned   | Milestone:
 Component:  Template system|   Version:
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  1  |   Needs_tests:  1 
Needs_better_patch:  1  |  
+---
Comment (by Alex):

 Please provide a single diff from the root of the source tree, rather than
 several files.

-- 
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] #2016: [patch] Decorator for template tags that load objects

[Django]

#2016: [patch] Decorator for template tags that load objects
+---
  Reporter:  ja...@pengale.com  | Owner:  nobody
Status:  assigned   | Milestone:
 Component:  Template system|   Version:
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  1  |   Needs_tests:  1 
Needs_better_patch:  1  |  
+---
Comment (by marcusf):

 Added my own attempt to provide an improved patch along with documentation
 and tests.

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

Re: [Django] #10911: Date comparison lookup operators

[Django]

#10911: Date comparison lookup operators
---+
  Reporter:  vbmendes  | Owner:  clement
  
Status:  new   | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version:  1.0
  
Resolution:|  Keywords:  lookup, 
orm, date
 Stage:  Accepted  | Has_patch:  0  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Comment (by fas):

 Soemthing for "older than 6 months" etc. would be great 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
-~--~~~~--~~--~--~---

[Django] #11881: ORDER BY in aggregate subqueries is not necessary and might causes on some SQL servers

[Django]

#11881: ORDER BY in aggregate subqueries is not necessary and might causes on 
some
SQL servers
--+-
 Reporter:  egenix_viktor |   
Owner:  nobody
   Status:  new   |   
Milestone:
Component:  Database layer (models, ORM)  | 
Version:  1.1   
 Keywords:  aggregate subquery order_by optimization incompatibility  |   
Stage:  Unreviewed
Has_patch:  1 |  
--+-
 Some SQL servers, like `MS SQL 2005` does not allow `ORDER BY` in
 subqueries without a `TOP` modifier. (It might apply to other database
 servers as well.) It is also suboptimal to use `ORDER BY` in the subquery
 of an aggregate `SELECT`, since it does not affect the result.

 It might be better to just clear ordering in the subquery in this case. I
 suggest adding the following line in the `BaseQuery.get_aggregation`
 method before the `query.add_subquery(obj)` call:

 {{{
 obj.clear_ordering(True)
 }}}

 Patch against the `db\models\sql\query.py` file of the 1.1 release version
 has been attached.

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