Re: [Django] #27279: Slow test framework initialization in 1.10.1 compared to 1.10

[Django]

#27279: Slow test framework initialization in 1.10.1 compared to 1.10
-+-
 Reporter:  mtomiyoshi   |Owner:  Simon
 Type:   |  Charette
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  1.10
 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 Simon Charette):

 * status:  new => assigned
 * owner:  nobody => Simon Charette
 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/7336 PR]

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.0ad75f4018c938916101bffe8d4adbe0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27279: Slow test framework initialization in 1.10.1 compared to 1.10

[Django]

#27279: Slow test framework initialization in 1.10.1 compared to 1.10
--+
 Reporter:  mtomiyoshi|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  1.10
 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
--+

Comment (by Marten Kenbeek):

 Sure, go ahead.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.66c3b01af01bbd92cf644de1a04404ff%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27279: Slow test framework initialization in 1.10.1 compared to 1.10

[Django]

#27279: Slow test framework initialization in 1.10.1 compared to 1.10
--+
 Reporter:  mtomiyoshi|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  1.10
 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
--+

Comment (by Simon Charette):

 Sorry for missing the 1.10.2 deadline.

 Thinking about it I like Marten's approach better as it deals with the
 limitation of `RenameModel.state_forwards()` directly and is easier to
 test.

 @Marten, do you mind if I submit a PR with your patch and tests I would
 add?

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.30a7317f500ecd3ac6bed14519b4a4b5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27279: Slow test framework initialization in 1.10.1 compared to 1.10

[Django]

#27279: Slow test framework initialization in 1.10.1 compared to 1.10
--+
 Reporter:  mtomiyoshi|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  1.10
 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 Claude Paroz):

 * stage:  Unreviewed => Accepted


Comment:

 Would be nice to have the optimization in 1.10.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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.f0dc029aeb2d2026a3c5f588b9ddb3ae%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27279: Slow test framework initialization in 1.10.1 compared to 1.10

[Django]

#27279: Slow test framework initialization in 1.10.1 compared to 1.10
-+-
 Reporter:  mtomiyoshi   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Migrations   |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by mtomiyoshi):

 Ok, so I did something stupid when trying Simon's suggestion and that's
 why it was so slow... Sorry about that!

 With a proper implementation of his suggestion the time to run an empty
 test got down to around 5-6 seconds in total, even better than what I was
 seeing with 1.10 (which was around 9-10 seconds). I also tried Marten's
 patch and it also runs around the same 5-6 seconds here, so I would say
 both implementations are great!

 Replying to [comment:9 Marten Kenbeek]:
 > Can you try the patch I've attached to the ticket? It may or may not
 make much of a difference compared to Simon's patch. If it doesn't make a
 difference, we can at least pinpoint the performance degradation to what
 happens ''during'' the `RenameModel.state_forwards()` method.
 >
 > For the profile files: could you use the `-o ` option? That
 will write all the raw profile data to the file, not just the output to
 stdout. We can then use the `pstats` module to analyze e.g. the
 caller/callee graph.
 >
 > > I am not sure if I understood correctly, but I tried setting a
 breakpoint on that return line and it got called only once (that one call
 > > was made by a RenameModel operation). Is this what you were expecting?
 >
 > With the regular 1.10.1, I would indeed expect this to be called once,
 when the first `RenameModel` accesses `state.apps`. With Simon's patch I
 would expect it to be called a few times: once for each migration
 containing a `RenameModel` operation, and once when rendering the final
 project state.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.5a695ca5d6a8c0fcce55181766a13b3a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27279: Slow test framework initialization in 1.10.1 compared to 1.10

[Django]

#27279: Slow test framework initialization in 1.10.1 compared to 1.10
-+-
 Reporter:  mtomiyoshi   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Migrations   |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Marten Kenbeek):

 Can you try the patch I've attached to the ticket? It may or may not make
 much of a difference compared to Simon's patch. If it doesn't make a
 difference, we can at least pinpoint the performance degradation to what
 happens ''during'' the `RenameModel.state_forwards()` method.

 For the profile files: could you use the `-o ` option? That
 will write all the raw profile data to the file, not just the output to
 stdout. We can then use the `pstats` module to analyze e.g. the
 caller/callee graph.

 > I am not sure if I understood correctly, but I tried setting a
 breakpoint on that return line and it got called only once (that one call
 > was made by a RenameModel operation). Is this what you were expecting?

 With the regular 1.10.1, I would indeed expect this to be called once,
 when the first `RenameModel` accesses `state.apps`. With Simon's patch I
 would expect it to be called a few times: once for each migration
 containing a `RenameModel` operation, and once when rendering the final
 project state.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.c7be5431de8a96b15df8f6dd72c7573a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27279: Slow test framework initialization in 1.10.1 compared to 1.10

[Django]

#27279: Slow test framework initialization in 1.10.1 compared to 1.10
-+-
 Reporter:  mtomiyoshi   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Migrations   |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Marten Kenbeek):

 * Attachment "renamemodel-reset-apps.patch" 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.7e6712f95149a3543302ab72fc4095cb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27279: Slow test framework initialization in 1.10.1 compared to 1.10

[Django]

#27279: Slow test framework initialization in 1.10.1 compared to 1.10
-+-
 Reporter:  mtomiyoshi   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Migrations   |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by mtomiyoshi):

 There are several other migrations (around 20-30) after one of those that
 uses a RenameModel, is this the cause of the slow startup? Or do you mean
 if there are several other operations inside these RenameModel migrations?

 I am not sure if I understood correctly, but I tried setting a breakpoint
 on that return line and it got called only once (that one call
 was made by a RenameModel operation). Is this what you were expecting?

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.2aed7f29bcf15cf868e2c7bfc1fd2a1f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27279: Slow test framework initialization in 1.10.1 compared to 1.10

[Django]

#27279: Slow test framework initialization in 1.10.1 compared to 1.10
-+-
 Reporter:  mtomiyoshi   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Migrations   |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 Replying to [comment:6 mtomiyoshi]:
 > I found 5 migrations with RenameModels on my project, so not that much,
 I think!

 If these migrations include a lot operations after these `RenameModel` it
 could be significantly slow.

 Could you try putting a breakpoint before
 
[https://github.com/django/django/blob/9c522d2ed8e752932bfff62d6e2940e56dee700b/django/db/migrations/state.py#L176
 this return statement] to make sure it's mostly triggered by
 `RenameModel.state_forwards` during the state mutation process.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.d5ad2f53b7d7692e849f20bc19d27c89%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27279: Slow test framework initialization in 1.10.1 compared to 1.10

[Django]

#27279: Slow test framework initialization in 1.10.1 compared to 1.10
-+-
 Reporter:  mtomiyoshi   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Migrations   |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by mtomiyoshi):

 I found 5 migrations with RenameModels on my project, so not that much, I
 think!

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.24798f8da1269d8c6fbd2ba93eaac015%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27279: Slow test framework initialization in 1.10.1 compared to 1.10

[Django]

#27279: Slow test framework initialization in 1.10.1 compared to 1.10
-+-
 Reporter:  mtomiyoshi   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Migrations   |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 Does you project include a lot of `RenameModel` operations? I might have
 missed operations that require accessing `state.apps` to perform
 `state_forwards`.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.772caa8be7754624f426a76da4d2aad1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27279: Slow test framework initialization in 1.10.1 compared to 1.10

[Django]

#27279: Slow test framework initialization in 1.10.1 compared to 1.10
-+-
 Reporter:  mtomiyoshi   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Migrations   |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by mtomiyoshi):

 I've attached the full profile report.

 I reran it two times with an empty test suite: the "profile1101" file is
 the regular Django 1.10.1 version but I also ran it with the Simon's
 suggested modification and the running time lowered by about 8 seconds.
 These results are on the "profile1101mod" file.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.a409ae0533a1c5baee7176e41996adf3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27279: Slow test framework initialization in 1.10.1 compared to 1.10

[Django]

#27279: Slow test framework initialization in 1.10.1 compared to 1.10
-+-
 Reporter:  mtomiyoshi   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Migrations   |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by mtomiyoshi):

 * Attachment "profile_results.tar.gz" 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.0e3baf5edb00f33ff176240a335882a0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27279: Slow test framework initialization in 1.10.1 compared to 1.10

[Django]

#27279: Slow test framework initialization in 1.10.1 compared to 1.10
-+-
 Reporter:  mtomiyoshi   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Migrations   |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 The final state has to be rendered to allow `post_migrate` to dispatch its
 `apps` argument even when `--keepdb` is used.

 The issue here is that during the process of computing the final state
 some operation's `state_forwards` might require access to `state.apps`
 triggering the rendering. I know that Markus has been working on teaching
 the migration framework to ''forward'' without accessing rendered model
 state but in this case we might be able to get away by preventing
 `reload_model()` from actually doing anything by deleting `state.apps`
 
[https://github.com/django/django/commit/d5c4ea524679a787fe11c927448e44e95646096b
 #diff-191c6b8087fd8fb2cc08a2d9f9bf44deR79 on every step] of `mutate_state`
 as `reload_model()` is a noop when `state.apps`
 
[https://github.com/django/django/blob/master/django/db/migrations/state.py#L104
 is missing].

 The `RenameModel.state_forwards()` operation still require access to
 `state.apps` (that should be fixed if possible in 1.11) so migrations
 containing them would still trigger an extra model rendering but the
 subsequent call to `render_model()` wouldn't until another `RenameModel`
 operation is performed.

 TL;DR adding a `delattr(state, 'apps', None)` before `mutate_state()`
 
[https://github.com/django/django/commit/d5c4ea524679a787fe11c927448e44e95646096b
 #diff-191c6b8087fd8fb2cc08a2d9f9bf44deR81 here] should speed up things
 significantly.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.f2975709ff8c451b5a71077d638c5ed6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27279: Slow test framework initialization in 1.10.1 compared to 1.10

[Django]

#27279: Slow test framework initialization in 1.10.1 compared to 1.10
-+-
 Reporter:  mtomiyoshi   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Migrations   |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Marten Kenbeek):

 * cc: marten.knbk@… (added)


Comment:

 Since you use `--keepdb`, the database should already have all migrations
 applied, and I think only the final project state should render all
 models. If that's the case, the number of calls to `ModelState.render()`
 (14865) is way higher than it should be.

 Could you provide the complete profile file for the 1.10.1 case? I'd like
 to take a closer look to see when those models are actually rendered.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.2ece2bd99a1630ffbd54bc78805e9dbe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27279: Slow test framework initialization in 1.10.1 compared to 1.10

[Django]

#27279: Slow test framework initialization in 1.10.1 compared to 1.10
-+-
 Reporter:  mtomiyoshi   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Migrations   |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * cc: Simon Charette (added)
 * needs_better_patch:   => 0
 * component:  Testing framework => Migrations
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Not sure what, if anything, can be done.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.d149151aba650887e252efb43d01c047%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.