Re: [Django] #32240: ConnectionAbortedError should be treated as a broken pipe error in the development server

2020-12-02 Thread Django 
#32240: ConnectionAbortedError should be treated as a broken pipe error in the
development server
-+-
 Reporter:  Petter Strandmark|Owner:  Petter
 |  Strandmark
 Type:  Uncategorized|   Status:  assigned
Component:  HTTP handling|  Version:  3.1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Petter Strandmark):

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

[Django] #32240: ConnectionAbortedError should be treated as a broken pipe error in the development server

2020-12-02 Thread Django 
#32240: ConnectionAbortedError should be treated as a broken pipe error in the
development server
-+-
   Reporter:  Petter |  Owner:  Petter Strandmark
  Strandmark |
   Type: | Status:  assigned
  Uncategorized  |
  Component:  HTTP   |Version:  3.1
  handling   |
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 People using Windows have been complaining about very long stack traces in
 the development server for a long time:
 - https://github.com/python/cpython/pull/9713
 - https://bugs.python.org/issue27682

 These happen under normal interaction with the development server using
 Chrome.

 I have fixed one issue in CPython in wsgiref, but I belive that we should
 also fix is_broken_pipe_error in django/core/servers/basehttp.py

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.d3e416ea2db10f890db4520f66338a90%40djangoproject.com.

Re: [Django] #32235: Set disabled prop on ReadOnlyPasswordHashField

2020-12-02 Thread Django 
#32235: Set disabled prop on ReadOnlyPasswordHashField
-+-
 Reporter:  Jaap Roes|Owner:  Timo
 Type:   |  Ludwig
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * stage:  Accepted => Ready for checkin


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.7fdb6754af40262297f1b2ba5129e55d%40djangoproject.com.

Re: [Django] #32191: Not RFC 6265 compliant cookies in contrib.messages.

2020-12-02 Thread Django 
#32191: Not RFC 6265 compliant cookies in contrib.messages.
--+---
 Reporter:  Nico Giefing  |Owner:  Craig Smith
 Type:  Bug   |   Status:  assigned
Component:  contrib.messages  |  Version:  3.1
 Severity:  Normal|   Resolution:
 Keywords:  Cookie malformed  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+---

Comment (by Craig Smith):

 Hi Florian, thanks for your feedback. I see what you mean about the Euro
 symbol and unicode characters in general. To get around this I added a
 `charset` parameter to the `compress/decompress` methods. So we can use
 utf-8 by default, but latin-1 where required.

 We need to use latin-1 in the `signing.dumps/loads` functions, since the
 `signing.JSONSerializer` uses it. Swapping it out leads us into that
 hornet's nest.

 The two tests that require latin-1 are
 `messages_tests.test_mixins.test_set_messages_success` and
 `messages_tests.test_cookie.test_cookie_settings`. This happens because of
 one or two calls to `storage.add` and `storage.update` . As an experiment
 I replaced all occurrences of latin-1 and iso-8859-1 with utf-8 to see if
 those tests would pass - they wouldn't. So it's from a dependency outside
 of django, most likely to do with WSGI, which uses latin-1 somehow. The
 bytes in particular are 0x91 and 0x92, which are left and right single
 quote characters in latin-1. Maybe we should open another ticket about
 removing the iso-8859-1 charset. Or at least pushing it back further
 toward the dependency boundary.

 I will get back onto this in a few days and come up with those extra
 tests. And then probably need to add documentation about the new methods.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.3325c424374b4e9d293b3cdf15120cb9%40djangoproject.com.

Re: [Django] #32236: LoginRequiredMixin and PermissionRequiredMixin could use UserPassesTestMixin

2020-12-02 Thread Django 
#32236: LoginRequiredMixin and PermissionRequiredMixin could use
UserPassesTestMixin
-+-
 Reporter:  Jaap Roes|Owner:  Jerin
 Type:   |  Peter George
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Jerin Peter George):

 * owner:  nobody => Jerin Peter George
 * status:  new => assigned


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.349f6e775721b4f2a199e503e60bbcc7%40djangoproject.com.

Re: [Django] #32239: FilteredRelation is not working with GenericRelation

2020-12-02 Thread Django 
#32239: FilteredRelation is not working with GenericRelation
-+-
 Reporter:  Omar Altayyan|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  FilteredRelation | Triage Stage:
  GenericRelation Generic Relation   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Omar Altayyan):

 my sincere apologies, thank u for your time, sorry for the inconvenience
 we have been working hard on this as it's causing us to do some hacks that
 slow down queries significantly, thank you for your thorough answer.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.94b2cf330dfd820dfa1e1ed76c784263%40djangoproject.com.

Re: [Django] #32239: FilteredRelation is not working with GenericRelation

2020-12-02 Thread Django 
#32239: FilteredRelation is not working with GenericRelation
-+-
 Reporter:  Omar Altayyan|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  FilteredRelation | Triage Stage:
  GenericRelation Generic Relation   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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


Comment:

 Please don't reopen this ticket without providing a sample project or new
 details. Yes, it works for me with Django 3.1.4, see my previous comment.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.c8272914c1ffb04d92aa4df810e5b69a%40djangoproject.com.

Re: [Django] #32239: FilteredRelation is not working with GenericRelation

2020-12-02 Thread Django 
#32239: FilteredRelation is not working with GenericRelation
-+-
 Reporter:  Omar Altayyan|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  FilteredRelation | Triage Stage:
  GenericRelation Generic Relation   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Omar Altayyan):

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


Comment:

 @Mariusz Felisiak
 did u try this on the latest stable django release of 3.1.4, because we
 tried the same exact code u posted without modification and it still
 ignored the last AND in the left outer join.
 could it be something solved in django's master branch and not released
 yet?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.97d21d34d57afa0d045ccd0d836b2ae7%40djangoproject.com.

Re: [Django] #32179: Add JSONObject Func

2020-12-02 Thread Django 
#32179: Add JSONObject Func
-+-
 Reporter:  Chiorufarewerin  |Owner:
 |  Chiorufarewerin
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  json_object, | Triage Stage:  Ready for
  jsonb_build_object, JSONObject |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"48b4bae983a1f9a73624fe62ef5bd1130b0dba39" 48b4bae9]:
 {{{
 #!CommitTicketReference repository=""
 revision="48b4bae983a1f9a73624fe62ef5bd1130b0dba39"
 Fixed #32179 -- Added JSONObject database function.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.6140214c9334e7dce2a5e00ce794fb17%40djangoproject.com.

Re: [Django] #32239: FilteredRelation is not working with GenericRelation

2020-12-02 Thread Django 
#32239: FilteredRelation is not working with GenericRelation
-+-
 Reporter:  Omar Altayyan|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  FilteredRelation | Triage Stage:
  GenericRelation Generic Relation   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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


Comment:

 I'm sorry but I don't see any new details, these are exactly the same
 models as in the ticket description, all works for me on the current
 master and with Django 3.1:
 {{{
 >>> qs = SomeEntity.objects.annotate(
 ...workspace_events=FilteredRelation('events',
 condition=Q(events__workspace_id=1)),
 ...limit=Coalesce('workspace_events__limit', 0,
 output_field=IntegerField()),
 ).values('id', 'workspace_events__id', 'limit').order_by('-limit')
 >>> print(qs.query)
 SELECT "ticket_32239_someentity"."id", workspace_events."id",
 COALESCE(workspace_events."limit", 0) AS "limit" FROM
 "ticket_32239_someentity" LEFT OUTER JOIN "ticket_32239_event"
 workspace_events ON ("ticket_32239_someentity"."id" =
 workspace_events."entity_id" AND (workspace_events."entity_type_id" = 10)
 AND (workspace_events."workspace_id" = 1)) ORDER BY "limit" DESC
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.8f1d20d8a8b7bcfcc8aa4c83ec0a3d9b%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2020-12-02 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  (none)
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Manav Agarwal):

 * owner:  Manav Agarwal => (none)
 * status:  assigned => 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.20a4c61ac2e21ace758baedebe49bc66%40djangoproject.com.

Re: [Django] #32239: FilteredRelation is not working with GenericRelation

2020-12-02 Thread Django 
#32239: FilteredRelation is not working with GenericRelation
-+-
 Reporter:  Omar Altayyan|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  FilteredRelation | Triage Stage:
  GenericRelation Generic Relation   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ammar-Shiekh):

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


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.c4952a86601097525e29dec8986276f5%40djangoproject.com.

Re: [Django] #32239: FilteredRelation is not working with GenericRelation

2020-12-02 Thread Django 
#32239: FilteredRelation is not working with GenericRelation
-+-
 Reporter:  Omar Altayyan|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  FilteredRelation | Triage Stage:
  GenericRelation Generic Relation   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Ammar-Shiekh):

 Here is the `test/models.py` file:


 {{{
 from django.db import models


 class Workspace(models.Model):
 pass

 class Event(models.Model):
 workspace = models.ForeignKey(Workspace, on_delete=models.CASCADE)

 limit = models.FloatField(default=0)

 entity_type = models.ForeignKey(ContentType, on_delete=models.CASCADE)
 entity_id = models.PositiveIntegerField()
 entity = GenericForeignKey('entity_type', 'entity_id')

 class Entity(models.Model):
 events = GenericRelation(Event, content_type_field='entity_type',
 object_id_field='entity_id')

 class Meta:
 abstract = True

 class SomeEntity(Entity):
 pass
 }}}

 After migrating these models to the database, try running the following
 code using `python manage.py shell`:

 {{{
 >>> from django.db.models import FilteredRelation
 >>> from django.db.models.functions import Coalesce
 >>> from test.models import SomeEntity
 >>> str(SomeEntity.objects.annotate(
 ... workspace_events=FilteredRelation('events',
 condition=Q(events__workspace_id=1)),
 ... limit=Coalesce('workspace_events__limit', 0),
 ... ).values('id', 'workspace_events__id',
 'limit').order_by('-limit').query)
 }}}

 The last command will print this:

 {{{
 'SELECT "test_someentity"."id", workspace_events."id",
 COALESCE(workspace_events."limit", 0) AS "limit" FROM "test_someentity"
 LEFT OUTER JOIN "test_event" workspace_events ON ("test_someentity"."id" =
 workspace_events."entity_id" AND (workspace_events."entity_type_id" =
 186)) ORDER BY "limit" DESC'
 }}}

 Notice that the condition on events workspace id specified by the
 FilteredRelation doesn't have an effect on the resulted query.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.6d9da861ba5757ddb30d1377848b%40djangoproject.com.

Re: [Django] #32235: Set disabled prop on ReadOnlyPasswordHashField

2020-12-02 Thread Django 
#32235: Set disabled prop on ReadOnlyPasswordHashField
-+-
 Reporter:  Jaap Roes|Owner:  Timo
 Type:   |  Ludwig
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Timo Ludwig):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/13741 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.490cf38e30e6a7d442a34d2576f46cf7%40djangoproject.com.

Re: [Django] #32236: LoginRequiredMixin and PermissionRequiredMixin could use UserPassesTestMixin

2020-12-02 Thread Django 
#32236: LoginRequiredMixin and PermissionRequiredMixin could use
UserPassesTestMixin
--+
 Reporter:  Jaap Roes |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Mariusz Felisiak):

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

Re: [Django] #32239: FilteredRelation is not working with GenericRelation

2020-12-02 Thread Django 
#32239: FilteredRelation is not working with GenericRelation
-+-
 Reporter:  Omar Altayyan|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  FilteredRelation | Triage Stage:
  GenericRelation Generic Relation   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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


Comment:

 Thanks for this report, however I cannot reproduce this issue with
 described models. Can you provide a sample project?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.5723e810cb2786502a222440fc467a54%40djangoproject.com.

Re: [Django] #32179: Add JSONObject Func

2020-12-02 Thread Django 
#32179: Add JSONObject Func
-+-
 Reporter:  Chiorufarewerin  |Owner:
 |  Chiorufarewerin
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  json_object, | Triage Stage:  Ready for
  jsonb_build_object, JSONObject |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.9aee8ba6c82e72e90d604d78a8a258b0%40djangoproject.com.