Re: [Django] #18575: Testing framework doesn't work without a SQL Database

[Django]

#18575: Testing framework doesn't work without a SQL Database
-+-
 Reporter:  delormemarco@…   |Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  1.4
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  regression   | 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 Claude Paroz ):

 In [changeset:"b4627bcabe6704c5bd1cbfb2d3a1421e05c29cd7"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b4627bcabe6704c5bd1cbfb2d3a1421e05c29cd7"
 [1.5.x] Fixed #18575 -- Empty DATABASES should default to dummy backend

 Thanks delormema...@gmail.com for the report.

 Backport of f1cc2be0c from master.
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18575: Testing framework doesn't work without a SQL Database

[Django]

#18575: Testing framework doesn't work without a SQL Database
-+-
 Reporter:  delormemarco@…   |Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  1.4
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  regression   | 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 Claude Paroz ):

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


Comment:

 In [changeset:"f1cc2be0c53858b673afc3b26347d3bb25e424f6"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f1cc2be0c53858b673afc3b26347d3bb25e424f6"
 Fixed #18575 -- Empty DATABASES should default to dummy backend

 Thanks delormema...@gmail.com 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 https://groups.google.com/groups/opt_out.

Re: [Django] #18575: Testing framework doesn't work without a SQL Database

[Django]

#18575: Testing framework doesn't work without a SQL Database
-+-
 Reporter:  delormemarco@…   |Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.4
 Severity:  Release blocker  |   Resolution:
 Keywords:  regression   | 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 aaugustin):

 To sum up, the patch for this ticket should:
 - activate the dummy backend when `settings.DATABASES` is empty,
 - change the default value in `global_settings.py` to match the
 documentation, and add a comment explaining that the dummy backend will be
 used if the setting is left empty,

 18575-3.diff is nearly RFC — it's only missing the comment.

 I checked with Carl on IRC that this is an improvement over #16873. At the
 time, no one had thought that people would write `DATABASES = {}` in their
 settings files, so this use case wasn't supported.

 Making the test runner aware of the dummy backend — so it doesn't attempt
 to create the database before the tests and drop it after — was forked to
 #19192.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18575: Testing framework doesn't work without a SQL Database

[Django]

#18575: Testing framework doesn't work without a SQL Database
-+-
 Reporter:  delormemarco@…   |Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.4
 Severity:  Release blocker  |   Resolution:
 Keywords:  regression   | 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 ptone):

 In handsight - I would have closed this as a dupe of #18053 instead of the
 other way - that ticket preceded this and represents the general case,
 while this is a specific case.

 A question we should ask is how can we leave the best trail for others to
 understand what is happening - at a minimum, I think we should add a
 comment to global_settings explaining that initialization will set the
 connection to use the dummy backend if not set in settings.py

 At that point I'm not sure whether having global settings be {} or leave
 it set to dummy backend as is currently the case matters - the comment
 will hopefully clarify for anyone who sets no DB or sets it to {} and
 wonders how the dummy backend got involved.

 Perhaps adding a TODO comment in the db.init code noting my idea in #18053
 of tweaking code to be explicit about when a DB is actually 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 https://groups.google.com/groups/opt_out.

Re: [Django] #18575: Testing framework doesn't work without a SQL Database

[Django]

#18575: Testing framework doesn't work without a SQL Database
-+-
 Reporter:  delormemarco@…   |Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.4
 Severity:  Release blocker  |   Resolution:
 Keywords:  regression   | 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 aaugustin):

 Claude's latest patch looks good. I'd like to hear from the people
 involved on #16873 before making a decision.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18575: Testing framework doesn't work without a SQL Database

[Django]

#18575: Testing framework doesn't work without a SQL Database
-+-
 Reporter:  delormemarco@…   |Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.4
 Severity:  Release blocker  |   Resolution:
 Keywords:  regression   | 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 aaugustin):

 This ticket essentially re-opens #16873.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18575: Testing framework doesn't work without a SQL Database

[Django]

#18575: Testing framework doesn't work without a SQL Database
-+-
 Reporter:  delormemarco@…   |Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.4
 Severity:  Release blocker  |   Resolution:
 Keywords:  regression   | 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):

 * owner:  nobody => aaugustin
 * status:  reopened => 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 https://groups.google.com/groups/opt_out.

Re: [Django] #18575: Testing framework doesn't work without a SQL Database

[Django]

#18575: Testing framework doesn't work without a SQL Database
-+-
 Reporter:  delormemarco@…   |Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Testing framework|  Version:  1.4
 Severity:  Release blocker  |   Resolution:
 Keywords:  regression   | 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 Architekt):

 * stage:  Accepted => Ready for checkin


Comment:

 Patch 3 reviewed.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18575: Testing framework doesn't work without a SQL Database

[Django]

#18575: Testing framework doesn't work without a SQL Database
---+
 Reporter:  delormemarco@… |Owner:  nobody
 Type:  Bug|   Status:  reopened
Component:  Testing framework  |  Version:  1.4
 Severity:  Release blocker|   Resolution:
 Keywords:  regression | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by claudep):

 #18053 was a duplicate. Read also the interesting comment from Preston
 (ticket:18053#comment:2)

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18575: Testing framework doesn't work without a SQL Database

[Django]

#18575: Testing framework doesn't work without a SQL Database
---+
 Reporter:  delormemarco@… |Owner:  nobody
 Type:  Bug|   Status:  reopened
Component:  Testing framework  |  Version:  1.4
 Severity:  Release blocker|   Resolution:
 Keywords:  regression | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by claudep):

 Replying to [comment:9 Architekt]:
 > I see here two problems:
 >
 > 1. In docs is default DATABASES setting empty dict. But when you set
 `DATABASES = {}` in project settings (which doesn't use dummy backend) it
 doesn't work like real default without any DATABASES in project settings
 (which uses dummy backend).

 Maybe this ticket could be solved by fixing the settings documentation
 (suggesting to not set DATABASES to {})? We could also add a note in the
 testing docs.

 > 2. Test runner does not know how to handle dummy database.

 I've created #19192 to track this issue (not a blocker).

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18575: Testing framework doesn't work without a SQL Database

[Django]

#18575: Testing framework doesn't work without a SQL Database
---+
 Reporter:  delormemarco@… |Owner:  nobody
 Type:  Bug|   Status:  reopened
Component:  Testing framework  |  Version:  1.4
 Severity:  Release blocker|   Resolution:
 Keywords:  regression | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Architekt):

 Yesterday I tried `DATABASES = {}` as author of this ticket did. This
 configuration is not loading dummy backend and everything raises
 ImproperlyConfigured. Even `manage.py shell` is not working. I checked
 comment in dummy backend base.py which says "Right now the dummy backend
 is there for raising ImproperlyConfigured if database configuration is
 missing." so I thinked that all those raises are correct and Django can't
 run without database settings.

 But with setting database engine as `django.db.backends.dummy` or removing
 whole databases configuration from settings is a different story. Shell
 works fine. Tests fail on creating database:
 {{{
 $ ./manage.py test myapp -v 2
 Creating test database for alias 'default' ('test_')...
 ImproperlyConfigured: settings.DATABASES is improperly configured. Please
 supply the ENGINE value. Check settings documentation for more details.
 }}}

 I see here two problems:

 1. In docs is default DATABASES setting empty dict. But when you set
 `DATABASES = {}` in project settings (which doesn't use dummy backend) it
 doesn't work like real default without any DATABASES in project settings
 (which uses dummy backend).

 2. Test runner does not know how to handle dummy database.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18575: Testing framework doesn't work without a SQL Database

[Django]

#18575: Testing framework doesn't work without a SQL Database
---+
 Reporter:  delormemarco@… |Owner:  nobody
 Type:  Bug|   Status:  reopened
Component:  Testing framework  |  Version:  1.4
 Severity:  Release blocker|   Resolution:
 Keywords:  regression | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by claudep):

 * status:  closed => reopened
 * resolution:  wontfix =>
 * severity:  Normal => Release blocker


Comment:

 We *want* to be able to use Django without a database. That's why we have
 a dummy backend after all (as Alex Gaynor reminded us on IRC).

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18575: Testing framework doesn't work without a SQL Database

[Django]

#18575: Testing framework doesn't work without a SQL Database
---+
 Reporter:  delormemarco@… |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.4
 Severity:  Normal |   Resolution:  wontfix
 Keywords:  regression | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Architekt):

 * cc: jan.bednarik@… (added)
 * status:  reopened => closed
 * resolution:   => wontfix
 * severity:  Release blocker => Normal


Comment:

 Did you notice that you can't run `python manage.py shell` without
 database?

 Patch doesn't work and it's impossible to fix this.

 When do you execute `from django.test import TestCase` in app/tests.py
 then Python executes `django.test.__init__`. There is imported one or more
 modules/classes which imports `django.db.connection` (or their dependency
 do). `django.test.client` is just first of them. If you remove it from
 `django.test.__init__`, then another module/class will import
 `django.db.connection`. And so on. Import from any module inside
 `django.db` will execute `django.db.__init__` which will raise exception
 `ImproperlyConfigured`.

 Defining default database (e.g. SQLite :memory:) will not break your code.
 So this is not not bug at all. Django just depends on database.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18575: Testing framework doesn't work without a SQL Database

[Django]

#18575: Testing framework doesn't work without a SQL Database
---+
 Reporter:  delormemarco@… |Owner:  nobody
 Type:  Bug|   Status:  reopened
Component:  Testing framework  |  Version:  1.4
 Severity:  Release blocker|   Resolution:
 Keywords:  regression | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by ptone):

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


Comment:

 Replying to [comment:5 melinath]:
 >Django clearly depends on the database for a lot of its functionality,
 and it's pretty simple to just use SQLite.

 The key bit there is that 'a lot of' != 'all of' - but more importantly
 this used to work, and so is a regression - even if it is an uncommon one.

 Unfortunately issues with the test framework are hard to test inside of
 Django - a little too recursive - and so will require some manual testing
 with sample projects.

 The django.test.client '''shouldn't''' be an issue, as you should be able
 to use straight python unittest

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18575: Testing framework doesn't work without a SQL Database

[Django]

#18575: Testing framework doesn't work without a SQL Database
---+-
 Reporter:  delormemarco@… |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.4
 Severity:  Release blocker|   Resolution:  needsinfo
 Keywords:  regression | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by melinath):

 * status:  new => closed
 * resolution:   => needsinfo
 * stage:  Ready for checkin => Accepted


Comment:

 Turns out the patch doesn't actually solve the issue, since django.db is
 imported in django.test.client, and ImproperlyConfigured is still raised.
 Ah well.

 That brings me back to my original reaction: Is there a benefit of
 supporting settings files that don't define any databases? Django clearly
 depends on the database for a lot of its functionality, and it's pretty
 simple to just use SQLite.

 If there is a use case that you feel needs to be addressed, please add
 some more information on it to the ticket and reopen 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 https://groups.google.com/groups/opt_out.

Re: [Django] #18575: Testing framework doesn't work without a SQL Database

[Django]

#18575: Testing framework doesn't work without a SQL Database
-+-
 Reporter:  delormemarco@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.4
 Severity:  Release blocker  |   Resolution:
 Keywords:  regression   | 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 melinath):

 * stage:  Accepted => Ready for checkin


Comment:

 Looks straightforward enough & addresses previous concerns. Tests still
 all passing... didn't think they wouldn't, but just ftr.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18575: Testing framework doesn't work without a SQL Database

[Django]

#18575: Testing framework doesn't work without a SQL Database
---+
 Reporter:  delormemarco@… |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.4
 Severity:  Release blocker|   Resolution:
 Keywords:  regression | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by aaugustin):

 The rewrite of `update_connections_time_zone ` isn't correct; signal
 receivers must accept `**kwargs` for forwards-compatibilty.

 I recommend restricting the patch to the changes required to fix this bug.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18575: Testing framework doesn't work without a SQL Database

[Django]

#18575: Testing framework doesn't work without a SQL Database
---+
 Reporter:  delormemarco@… |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.4
 Severity:  Release blocker|   Resolution:
 Keywords:  regression | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by claudep):

 * 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 https://groups.google.com/groups/opt_out.

Re: [Django] #18575: Testing framework doesn't work without a SQL Database

[Django]

#18575: Testing framework doesn't work without a SQL Database
---+
 Reporter:  delormemarco@… |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.4
 Severity:  Release blocker|   Resolution:
 Keywords:  regression | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by claudep):

 * severity:  Normal => Release blocker
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * keywords:   => regression
 * needs_docs:   => 0
 * stage:  Unreviewed => Accepted


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