Re: [Django] #32975: ModelAdmin for proxy model with InlineModelAdmin for proxy superclass reference results in admin.E202

2021-09-02 Thread Django 
#32975: ModelAdmin for proxy model with InlineModelAdmin for proxy superclass
reference results in admin.E202
-+-
 Reporter:  Lucas Weyne  |Owner:  Taulant
 |  Aliraj
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  3.1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  proxy,   | Triage Stage:  Ready for
  InlineModelAdmin, E202 |  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:"0e8be73812a6e62d5a6b12a585d133b56bc2bf52" 0e8be738]:
 {{{
 #!CommitTicketReference repository=""
 revision="0e8be73812a6e62d5a6b12a585d133b56bc2bf52"
 Fixed #32975 -- Fixed admin system check for inlines with foreign keys to
 proxy models.
 }}}

-- 
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/068.e0e6f46bb0bb492ca949399f2e89d6ee%40djangoproject.com.

Re: [Django] #32975: ModelAdmin for proxy model with InlineModelAdmin for proxy superclass reference results in admin.E202

2021-09-02 Thread Django 
#32975: ModelAdmin for proxy model with InlineModelAdmin for proxy superclass
reference results in admin.E202
-+-
 Reporter:  Lucas Weyne  |Owner:  Taulant
 |  Aliraj
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  3.1
 Severity:  Normal   |   Resolution:
 Keywords:  proxy,   | Triage Stage:  Ready for
  InlineModelAdmin, E202 |  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/068.edf1e5b63e455b3e393b2afa4411e93e%40djangoproject.com.

Re: [Django] #29115: Allow rendering of admin forms with Jinja2

2021-09-02 Thread Django 
#29115: Allow rendering of admin forms with Jinja2
---+
 Reporter:  Joey Wilhelm   |Owner:  Joey Wilhelm
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  dev
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by David Smith):

 When reviewing [https://github.com/django/django/pull/14819/files PR14819]
 it was noticed that `django.forms.utils.flatatt()` is now only used once
 by `AdminReadonlyField.label_tag()` and could be removed as part of the
 fix for this ticket, see
 [https://github.com/django/django/pull/14819/files#r700347711 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/069.28dbe2d8aae19f230466719f49b9aebd%40djangoproject.com.

Re: [Django] #31907: Inconsistent key validation checks in cache backends.

2021-09-02 Thread Django 
#31907: Inconsistent key validation checks in cache backends.
-+-
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:  Bug  |   Status:  closed
Component:  Core (Cache system)  |  Version:  dev
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"b8824e8d17434957650517370f739e340867c381" b8824e8]:
 {{{
 #!CommitTicketReference repository=""
 revision="b8824e8d17434957650517370f739e340867c381"
 Refs #31907 -- Fixed incorrect argument for delete_many() in cache tests.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.f67144bce73497f129e2286364f7d24e%40djangoproject.com.

Re: [Django] #31867: Inconsistency rendering hidden fields with view-only permissions in admin

2021-09-02 Thread Django 
#31867: Inconsistency rendering hidden fields with view-only permissions in 
admin
-+-
 Reporter:  Antoine Humbert  |Owner:  Antoine
 |  Humbert
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:  admin hidden field   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Carlton Gibson):

 * 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/072.4cf66b289f464f2c08d826ce859da296%40djangoproject.com.

Re: [Django] #32492: Add django API for Postgres pg_trgm word_similarity, fuzzy full-text search.

2021-09-02 Thread Django 
#32492: Add django API for Postgres pg_trgm word_similarity, fuzzy full-text
search.
-+-
 Reporter:  Taneli   |Owner:  Nikita
 |  Marchant
 Type:  New feature  |   Status:  assigned
Component:  contrib.postgres |  Version:  dev
 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 Nikita Marchant):

 * owner:  (none) => Nikita Marchant


-- 
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.7abb1d47dd91319ea65ffd906156849d%40djangoproject.com.

Re: [Django] #32492: Add django API for Postgres pg_trgm word_similarity, fuzzy full-text search.

2021-09-02 Thread Django 
#32492: Add django API for Postgres pg_trgm word_similarity, fuzzy full-text
search.
--+
 Reporter:  Taneli|Owner:  (none)
 Type:  New feature   |   Status:  assigned
Component:  contrib.postgres  |  Version:  dev
 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 Nikita Marchant):

 * owner:  Taneli => (none)


-- 
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.c5f597e1a4ce9a2f3a8de9dae3a9713c%40djangoproject.com.

Re: [Django] #33012: Add a Redis cache backend.

2021-09-02 Thread Django 
#33012: Add a Redis cache backend.
-+-
 Reporter:  Carlton Gibson   |Owner:  Daniyal
 |  Abbasi
 Type:  New feature  |   Status:  assigned
Component:  Core (Cache system)  |  Version:  4.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"dca4c2ff764ab94848274952eee4319a638be1d2" dca4c2ff]:
 {{{
 #!CommitTicketReference repository=""
 revision="dca4c2ff764ab94848274952eee4319a638be1d2"
 Refs #33012 -- Moved PickleSerializer to django.core.serializers.base and
 added tests.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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/071.3a9dfe76ea714aa2d28abdb20ddfb969%40djangoproject.com.

Re: [Django] #33082: test_subparser_invalid_option regression with Python 3.9.7

2021-09-02 Thread Django 
#33082: test_subparser_invalid_option regression with Python 3.9.7
-+-
 Reporter:  Michał Górny |Owner:  Mariusz
 Type:   |  Felisiak
  Cleanup/optimization   |   Status:  closed
Component:  Core (Other) |  Version:  3.2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"05bc1c81aa590bcbd508bdeafb16d1884c92b4ea" 05bc1c81]:
 {{{
 #!CommitTicketReference repository=""
 revision="05bc1c81aa590bcbd508bdeafb16d1884c92b4ea"
 [2.2.x] Fixed #33082 -- Fixed CommandTests.test_subparser_invalid_option
 on Python 3.9.7+.

 Thanks Michał Górny for the report.

 Backport of 50ed545e2fa02c51e0d1559b83624f256e4b499b from main.
 }}}

-- 
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/064.d38024d19581f4328de90d78bd5d41f8%40djangoproject.com.

Re: [Django] #33082: test_subparser_invalid_option regression with Python 3.9.7

2021-09-02 Thread Django 
#33082: test_subparser_invalid_option regression with Python 3.9.7
-+-
 Reporter:  Michał Górny |Owner:  Mariusz
 Type:   |  Felisiak
  Cleanup/optimization   |   Status:  closed
Component:  Core (Other) |  Version:  3.2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"9dd1f9572fa5024deb1615266a0cd9995b27bd41" 9dd1f957]:
 {{{
 #!CommitTicketReference repository=""
 revision="9dd1f9572fa5024deb1615266a0cd9995b27bd41"
 [3.1.x] Fixed #33082 -- Fixed CommandTests.test_subparser_invalid_option
 on Python 3.9.7+.

 Thanks Michał Górny for the report.

 Backport of 50ed545e2fa02c51e0d1559b83624f256e4b499b from main.
 }}}

-- 
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/064.f1e4950f779ead72c37fcba2960c7876%40djangoproject.com.

Re: [Django] #33082: test_subparser_invalid_option regression with Python 3.9.7

2021-09-02 Thread Django 
#33082: test_subparser_invalid_option regression with Python 3.9.7
-+-
 Reporter:  Michał Górny |Owner:  Mariusz
 Type:   |  Felisiak
  Cleanup/optimization   |   Status:  closed
Component:  Core (Other) |  Version:  3.2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"b61f44c339830ea53663415f00cbd17e2fd5aa43" b61f44c]:
 {{{
 #!CommitTicketReference repository=""
 revision="b61f44c339830ea53663415f00cbd17e2fd5aa43"
 [3.2.x] Fixed #33082 -- Fixed CommandTests.test_subparser_invalid_option
 on Python 3.9.7+.

 Thanks Michał Górny for the report.

 Backport of 50ed545e2fa02c51e0d1559b83624f256e4b499b from main.
 }}}

-- 
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/064.f85a3e8cc1a3c0a86f117f6449471aae%40djangoproject.com.

Re: [Django] #33082: test_subparser_invalid_option regression with Python 3.9.7

2021-09-02 Thread Django 
#33082: test_subparser_invalid_option regression with Python 3.9.7
-+-
 Reporter:  Michał Górny |Owner:  Mariusz
 Type:   |  Felisiak
  Cleanup/optimization   |   Status:  closed
Component:  Core (Other) |  Version:  3.2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by GitHub ):

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


Comment:

 In [changeset:"50ed545e2fa02c51e0d1559b83624f256e4b499b" 50ed545e]:
 {{{
 #!CommitTicketReference repository=""
 revision="50ed545e2fa02c51e0d1559b83624f256e4b499b"
 Fixed #33082 -- Fixed CommandTests.test_subparser_invalid_option on Python
 3.9.7+.

 Thanks Michał Górny 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 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/064.95174dbf21c8af2d5bac8fe0986f89b8%40djangoproject.com.

Re: [Django] #32975: ModelAdmin for proxy model with InlineModelAdmin for proxy superclass reference results in admin.E202

2021-09-02 Thread Django 
#32975: ModelAdmin for proxy model with InlineModelAdmin for proxy superclass
reference results in admin.E202
-+-
 Reporter:  Lucas Weyne  |Owner:  Taulant
 |  Aliraj
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  3.1
 Severity:  Normal   |   Resolution:
 Keywords:  proxy,   | Triage Stage:  Accepted
  InlineModelAdmin, E202 |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_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/068.88349c10caae4edc9ed0025c9533ff85%40djangoproject.com.

Re: [Django] #33082: test_subparser_invalid_option regression with Python 3.9.7

2021-09-02 Thread Django 
#33082: test_subparser_invalid_option regression with Python 3.9.7
-+-
 Reporter:  Michał Górny |Owner:  Mariusz
 Type:   |  Felisiak
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * 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/064.b93445c734c55527bff1672d492e1693%40djangoproject.com.

Re: [Django] #3482: MultipleChoiceField validation against a list with a single null element

2021-09-02 Thread Django 
#3482: MultipleChoiceField validation against a list with a single null element
-+-
 Reporter:  Jeff Bauer   |Owner:  nobody
   |
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  dev
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  MultipleChoiceField  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

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


Comment:

 So, it's hard to say about the dark-history here, as bootstrapping a very
 old environment is somewhat fiddly these days but
 
[https://github.com/django/django/blob/d0ea01af2814e276c4a090e599d5fd11c6ce4bf8/django/forms/fields.py#L884-L890
 the logic here] is virtually unchanged from the
 
[https://github.com/django/django/commit/6645d1fe48868814e4c73056b68be5c3861ed2d0
 #diff-
 19fae1b4e3786d4af8cdf8db08d18d687caeae43859b35c769deb96d3aacf05cR256-R260
 earliest days of the MultipleChoiceField implementation]. It's certainly
 unchanged as far back as Django 1.8. Without a serious case being made,
 the backwards compatibility concerns preclude changing this now.

 However, for me, this is expected behaviour: `''` is **not** a valid
 choice. If I want filtering of empty values then I'm expecting to use a
 widget to filter this in `value_from_datadict`, or else a field subclass,
 if I want the behaviour there. The default implementation is doing the
 right thing here rejecting the incorrect value.

-- 
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/087.ab570d04b62d826178c390b9a387%40djangoproject.com.

Re: [Django] #33082: test_subparser_invalid_option regression with Python 3.9.7

2021-09-02 Thread Django 
#33082: test_subparser_invalid_option regression with Python 3.9.7
-+-
 Reporter:  Michał Górny |Owner:  Mariusz
 Type:   |  Felisiak
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  3.2
 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 Mariusz Felisiak):

 * status:  new => assigned
 * component:  Uncategorized => Core (Other)
 * owner:  nobody => Mariusz Felisiak
 * has_patch:  0 => 1
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 Ahh yes, see
 
https://github.com/python/cpython/commit/097801844c99ea3916bebe1cc761257ea7083d34.
 Thanks for the report.

 I don't think it's worth switching msg between Python versions,
 [https://github.com/django/django/pull/14826 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/064.2eb65c277b6f84d7fcb940bacc8734e4%40djangoproject.com.

Re: [Django] #24018: Support journal_mode=WAL for sqlite

2021-09-02 Thread Django 
#24018: Support journal_mode=WAL for sqlite
-+-
 Reporter:  Curtis Maloney   |Owner:  Aaron
 |  Linville
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Carlton Gibson):

 Maybe allowing `PRAGMAS` to be set is a good idea, in general (e.g.
 #31765) but the WAL setting is persistent:

 > The persistence of WAL mode means that applications can be converted to
 using SQLite in WAL mode without making any changes to the application
 itself. One has merely to run "PRAGMA journal_mode=WAL;" on the database
 file(s) using the command-line shell or other utility, then restart the
 application. [https://sqlite.org/wal.html#persistence_of_wal_mode SQLite
 Docs].

 So narrowly, running that a single time is sufficient, and an entry in the
 [https://docs.djangoproject.com/en/3.2/ref/databases/#sqlite-notes SQLite
 notes] may be the quickest route forward (for this narrower issue).

-- 
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.c27cc39870460f754f134dea796a08ab%40djangoproject.com.