Re: [Django] #15124: BooleanField should not use False as default (unless provided)

2011-01-30 Thread Django 
#15124: BooleanField should not use False as default (unless provided)
+---
   Reporter:  andrewbadr| Owner:  
nobody  
 Status:  new   | Milestone:
  
  Component:  Database layer (models, ORM)  |   Version:  
1.3-beta
 Resolution:|  Keywords:
  
   Triage Stage:  Design decision needed| Has patch:  1 
  
Needs documentation:  0 |   Needs tests:  0 
  
Patch needs improvement:  0 |  
+---

Comment (by Alex):

 So apparently I hadn't noticed this before, but this will almost certainly
 break code I have, likely others as well.

-- 
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] #15124: BooleanField should not use False as default (unless provided)

2011-01-30 Thread Django 
#15124: BooleanField should not use False as default (unless provided)
+---
   Reporter:  andrewbadr| Owner:  
nobody  
 Status:  new   | Milestone:
  
  Component:  Database layer (models, ORM)  |   Version:  
1.3-beta
 Resolution:|  Keywords:
  
   Triage Stage:  Design decision needed| Has patch:  1 
  
Needs documentation:  0 |   Needs tests:  0 
  
Patch needs improvement:  0 |  
+---
Changes (by andrewbadr):

  * has_patch:  0 => 1
  * version:  1.2 => 1.3-beta


-- 
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] #13488: Exceptions in GEOS I/O object destructor at process exit

2011-01-30 Thread Django 
#13488: Exceptions in GEOS I/O object destructor at process exit
+---
   Reporter:  mroach@…  | Owner:  jbronn
 Status:  reopened  | Milestone:  1.3   
  Component:  GIS   |   Version:  1.2   
 Resolution:|  Keywords:  gis   
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  1 |  
+---
Changes (by sheats):

 * cc: sheats@… (added)


Comment:

 I just tried the patch and it works fine -- error message goes away
 completely.  How refreshing!

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

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

Re: [Django] #15130: Model.validate_unique method doesn't take in account multi-db

2011-01-30 Thread Django 
#15130: Model.validate_unique method doesn't take in account multi-db
---+
   Reporter:  t2y  | Owner:  
 Status:  reopened | Milestone:  1.3 
  Component:  ORM aggregation  |   Version:  1.2 
 Resolution:   |  Keywords:  multi-db
   Triage Stage:  Accepted | Has patch:  1   
Needs documentation:  0|   Needs tests:  0   
Patch needs improvement:  1|  
---+
Changes (by ramiro):

  * needs_better_patch:  0 => 1


Comment:

 Russell suggested to avoid modifying `._state.db` so test were changed so
 the fist model is saved to the 'other' DB and the second one to the
 'default' DB:

 {{{
 #!python
 class MultiDbUniqueTests(TestCase):
 multi_db = True

 def test_unique_multi_db_isolation(self):
 "Attempt to save two model instances that don't pass Field.unique
 checks to different DBs."
 UniqueFieldsModel(unique_charfield='Hello world',
 unique_integerfield=42, non_unique_field=3).save(using='other')
 b = UniqueFieldsModel(unique_charfield='Hello world',
 unique_integerfield=42, non_unique_field=3)
 try:
 b.full_clean()
 except ValidationError:
 self.fail("unique field validation shouldn't erroneosuly
 trigger when the identical model instances are on different databases.")
 else:
 b.save()
 self.assertEqual(UniqueFieldsModel.objects.using('default').count(), 1)
 self.assertEqual(UniqueFieldsModel.objects.using('other').count(), 1)

 def test_unique_together_multi_db_isolation(self):
 "Attempt to save two model instances that don't pass
 Meta.unique_together checks to different DBs."
 UniqueTogetherModel(cfield='Hello world', ifield=42,
 efield='u...@example.org').save(using='other')
 b = UniqueTogetherModel(cfield='Hello world', ifield=42,
 efield='u...@example.org')
 try:
 b.full_clean()
 except ValidationError:
 self.fail("Meta.unique_together validation shouldn't
 erroneosuly trigger when the identical model instances are on different
 databases.")
 else:
 b.save()
 self.assertEqual(UniqueTogetherModel.objects.using('default').count(), 1)
 self.assertEqual(UniqueTogetherModel.objects.using('other').count(), 1)

 def test_unique_for_x_multi_db_isolation(self):
 "Attempt to save two model instances that don't pass
 Field.unique_for checks to different DBs."
 today = datetime.date.today()
 now = datetime.datetime.now()
 UniqueForDateModel(start_date=today, end_date=now, count=314,
 order=21, name='Foo').save(using='other')
 b = UniqueForDateModel(start_date=today, end_date=now, count=314,
 order=21, name='Foo')
 try:
 b.full_clean()
 except ValidationError:
 self.fail("Meta.unique_for_* validation shouldn't erroneosuly
 trigger when the identical model instances are on different databases.")
 else:
 b.save()
 self.assertEqual(UniqueForDateModel.objects.using('default').count(), 1)
 self.assertEqual(UniqueForDateModel.objects.using('other').count(), 1)
 }}}

 Problem is: In this case these tests don't fail if the changes to
 `django/db/models/base.py` are undone.

 So it seems there is some deeper problem 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] #15195: TestFramework doesn't set DEBUG to TRUE

2011-01-30 Thread Django 
#15195: TestFramework doesn't set DEBUG to TRUE
-+--
   Reporter:  jbcurtin   | Owner:  jbcurtin 
   
 Status:  closed | Milestone:  1.3  
   
  Component:  Testing framework  |   Version:  1.2  
   
 Resolution:  wontfix|  Keywords:  test conf debug 
settings
   Triage Stage:  Unreviewed | Has patch:  1
   
Needs documentation:  0  |   Needs tests:  0
   
Patch needs improvement:  0  |  
-+--
Changes (by ramiro):

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


Comment:

 This is by design: http://docs.djangoproject.com/en/dev/topics/testing
 /#other-test-conditions

 ''Regardless of the value of the DEBUG setting in your configuration file,
 all Django tests run with DEBUG=False. This is to ensure that the observed
 output of your code matches what will be seen in a production setting.''

-- 
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] #15196: Documentation still says it's 1.2

2011-01-30 Thread Django 
#15196: Documentation still says it's 1.2
-+--
   Reporter:  ericholscher   | Owner:  nobody
 Status:  closed | Milestone:
  Component:  Uncategorized  |   Version:  SVN   
 Resolution:  fixed  |  Keywords:
   Triage Stage:  Unreviewed | Has patch:  0 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by jezdez):

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


Comment:

 Fixed in [15374].

-- 
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] #15196: Documentation still says it's 1.2

2011-01-30 Thread Django 
#15196: Documentation still says it's 1.2
---+
 Reporter:  ericholscher   |  Owner:  nobody
   Status:  new|  Milestone:
Component:  Uncategorized  |Version:  SVN   
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  
---+
 The documentation still claims that it's version 1.2. It should probably
 be updated to say 1.3alpha or whatever, or whatever the main django's
 version declares.

 https://github.com/django/django/blob/master/docs/conf.py#L53

-- 
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] #15195: TestFramework doesn't set DEBUG to TRUE

2011-01-30 Thread Django 
#15195: TestFramework doesn't set DEBUG to TRUE
--+-
 Reporter:  jbcurtin  |  Owner:  jbcurtin  
   Status:  new   |  Milestone:  1.3   
Component:  Testing framework |Version:  1.2   
 Keywords:  test conf debug settings  |   Triage Stage:  Unreviewed
Has patch:  1 |  
--+-
 Qucikfix:[[BR]]
 from django.conf import settings[[BR]]
 settings.DEBUG = True[[BR]]
 Feel free to tell me were I need to go to register for an account to make
 the change myself and submit it to the code base.

-- 
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] #15110: User Isolation between sites.

2011-01-30 Thread Django 
#15110: User Isolation between sites.
-+--
   Reporter:  jorgeecardona  | Owner:  nobody  
 Status:  new| Milestone:  2.0 
  Component:  Contrib apps   |   Version:  1.2 
 Resolution: |  Keywords:  multitenancy
   Triage Stage:  Someday/Maybe  | Has patch:  1   
Needs documentation:  1  |   Needs tests:  0   
Patch needs improvement:  0  |  
-+--
Changes (by NicoEchaniz):

 * cc: NicoEchaniz (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] #15089: contrib.sites and multitenancy

2011-01-30 Thread Django 
#15089: contrib.sites and multitenancy
--+-
   Reporter:  legutierr   | Owner:  nobody  
 Status:  new | Milestone:  
  Component:  Contrib apps|   Version:  1.3-beta
 Resolution:  |  Keywords:  
   Triage Stage:  Design decision needed  | Has patch:  1   
Needs documentation:  0   |   Needs tests:  0   
Patch needs improvement:  1   |  
--+-
Changes (by NicoEchaniz):

 * cc: NicoEchaniz (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] #15191: Minor grammar fix in form validation docs

2011-01-30 Thread Django 
#15191: Minor grammar fix in form validation docs
-+--
   Reporter:  berto  | Owner:  nobody
 Status:  closed | Milestone:
  Component:  Documentation  |   Version:  1.2   
 Resolution:  fixed  |  Keywords:
   Triage Stage:  Accepted   | Has patch:  1 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by timo):

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


Comment:

 Fixed in [15372]

-- 
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] #14978: Add versionchanged note to ––adminmedia docs

2011-01-30 Thread Django 
#14978: Add versionchanged note to ––adminmedia docs
-+--
   Reporter:  sehmaschine@…  | Owner:  nobody
 Status:  closed | Milestone:  1.3   
  Component:  Documentation  |   Version:  SVN   
 Resolution:  fixed  |  Keywords:
   Triage Stage:  Accepted   | Has patch:  0 
Needs documentation:  1  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by jezdez):

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


Comment:

 Fixed in [15370].

-- 
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] #13007: Django fails to log in when a cookie is set on the same domain containing a colon

2011-01-30 Thread Django 
#13007: Django fails to log in when a cookie is set on the same domain 
containing a
colon
-+--
   Reporter:  Warlax | Owner:  nobody   
 
 Status:  reopened   | Milestone:  1.3  
 
  Component:  HTTP handling  |   Version:  SVN  
 
 Resolution: |  Keywords:  cookies, 
sprintdec2010
   Triage Stage:  Accepted   | Has patch:  1
 
Needs documentation:  0  |   Needs tests:  0
 
Patch needs improvement:  1  |  
-+--
Changes (by russellm):

  * needs_better_patch:  0 => 1
  * stage:  Ready for checkin => Accepted


Comment:

 This patch doesn't apply clean to trunk, and it's not obvious how to adapt
 the patch -- there have been other modifications to the cookie code in the
 interim.

-- 
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] #15177: Tell users about the new class based generic views in old generic views documentation

2011-01-30 Thread Django 
#15177: Tell users about the new class based generic views in old generic views
documentation
-+--
   Reporter:  rasca  | Owner:  rasca
 Status:  closed | Milestone:  1.3  
  Component:  Documentation  |   Version:  SVN  
 Resolution:  fixed  |  Keywords:   
   Triage Stage:  Ready for checkin  | Has patch:  1
Needs documentation:  0  |   Needs tests:  0
Patch needs improvement:  0  |  
-+--
Changes (by russellm):

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


Comment:

 (In [15367]) Fixed #15177 -- Added note to generic views reference page
 indicating that the views have been deprecated (mirroring the topic
 guide). Thanks to rasca for the report and 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] #15134: modelforms documentation appears twice in doctree

2011-01-30 Thread Django 
#15134: modelforms documentation appears twice in doctree
-+--
   Reporter:  Aryeh Leib Taurog   | 
Owner:  nobody
 Status:  closed | 
Milestone:
  Component:  Documentation  |   
Version:  1.2   
 Resolution:  fixed  |  
Keywords:
   Triage Stage:  Ready for checkin  | Has 
patch:  0 
Needs documentation:  0  |   Needs 
tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by russellm):

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


Comment:

 (In [15366]) Fixed #15134 -- Removed a duplicate TOC entry for modelforms
 docs. Thanks to Aryeh Leib Taurog for the report.

-- 
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] #15194: Need 'geos_c' as library name for Windows

2011-01-30 Thread Django 
#15194: Need 'geos_c' as library name for Windows
+---
 Reporter:  master  |  Owner:  nobody
   Status:  new |  Milestone:
Component:  GIS |Version:  1.2   
 Keywords:  geos_c  |   Triage Stage:  Unreviewed
Has patch:  0   |  
+---
 The OSGeo4W project (http://trac.osgeo.org/osgeo4w/) provides the GEOS
 library as 'geos_c.dll' (by default in C:\OSGeo4W\bin\).

 So adding the name 'geos_c' in gis/geos/libgeos.py in the "os.name ==
 'nt'" case would be nice and save us the pain to set a GEOS_LIBRARY_PATH
 setting.

 By the way, who provides the lib as 'libgeos_c-1' ? Cygwin ? A comment
 about originators is welcome.

-- 
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] #14698: django.utils.module_loading.module_has_submodule yields false positives

2011-01-30 Thread Django 
#14698: django.utils.module_loading.module_has_submodule yields false positives
-+--
   Reporter:  lrekucki   | Owner:  nobody
 Status:  closed | Milestone:  1.3   
  Component:  Core framework |   Version:  1.2   
 Resolution:  fixed  |  Keywords:
   Triage Stage:  Ready for checkin  | Has patch:  1 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by russellm):

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


Comment:

 (In [15362]) Fixed #14698 -- Ensure that module_has_sumodule doesn't
 mistake a cache miss for an existent package. Thanks to Łukasz Rekucki for
 the report and patch, and to shields for the test case.

-- 
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] #15187: CommonMiddleware should only send broken link emails if DEBUG is False

2011-01-30 Thread Django 
#15187: CommonMiddleware should only send broken link emails if DEBUG is False
-+--
   Reporter:  dancarroll | Owner:  dancarroll   
 Status:  closed | Milestone:   
  Component:  Core framework |   Version:  1.2  
 Resolution:  fixed  |  Keywords:  common middleware
   Triage Stage:  Ready for checkin  | Has patch:  1
Needs documentation:  0  |   Needs tests:  0
Patch needs improvement:  0  |  
-+--
Changes (by russellm):

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


Comment:

 (In [15363]) Fixed #15187 -- Ensure that missing page emails aren't sent
 when running under debug. Thanks to Dan Carroll for the report and 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] #13570: SMTP backend should try harder to figure out the local host name

2011-01-30 Thread Django 
#13570: SMTP backend should try harder to figure out the local host name
+---
   Reporter:  jacob | Owner:  sernin
 Status:  assigned  | Milestone:  1.3   
  Component:  django.core.mail  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  1 
Patch needs improvement:  1 |  
+---
Changes (by russellm):

  * needs_better_patch:  0 => 1
  * needs_tests:  0 => 1
  * stage:  Ready for checkin => Accepted


Comment:

 Sorry - but this isn't RFC.

 It doesn't contain a test case, and it doesn't contain a compelling
 argument for why tests aren't plausible. It doesn't even contain a clear
 description of why the change is needed other than suggesting "certain
 circumstances" under which it will be needed.

 It also seems to assume that the result of
 socket.gethostbyname(socket.gethostname()) will be an IPv6 address, which
 I'm pretty sure isn't correct.

-- 
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] #6148: Add generic support for database schemas

2011-01-30 Thread Django 
#6148: Add generic support for database schemas
+---
   Reporter:  ikelly| Owner:
 
 Status:  new   | Milestone:
 
  Component:  Database layer (models, ORM)  |   Version:  SVN   
 
 Resolution:|  Keywords:  
oracle postgresql mysql schemas
   Triage Stage:  Accepted  | Has patch:  1 
 
Needs documentation:  0 |   Needs tests:  0 
 
Patch needs improvement:  1 |  
+---
Changes (by ramiro):

  * owner:  ramiro =>


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