Re: [Django] #30728: Django urls patterns resolver shadowing exceptions thrown everywhere else

[Django]

#30728: Django urls patterns resolver shadowing exceptions thrown everywhere 
else
-+--
 Reporter:  Ariel Torti  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Utilities|  Version:  2.2
 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 Ariel Torti):

 * component:  Core (URLs) => Utilities


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

Re: [Django] #30728: Django urls patterns resolver shadowing exceptions thrown everywhere else

[Django]

#30728: Django urls patterns resolver shadowing exceptions thrown everywhere 
else
-+--
 Reporter:  maks500  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (URLs)  |  Version:  2.2
 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
-+--
Description changed by maks500:

Old description:

> The new version of django somehow captures all the exceptions ocurred
> while parsing the urlpatterns.
>
> How to reproduce:
>   * Create a django project
>   * Create a an app
>
> app/views.py
> {{{
> from django.shortcuts import render
>
> class MyCustomExceptionShadowed(Exception):
>   pass
>
> raise MyCustomExceptionShadowed('I have a description of your error')
>
> # Create your views here.
> def myview(request):
>   pass
> }}}
>
> urls.py
> {{{
> from django.contrib import admin
> from django.urls import path
>
> from bugtest import views
>
> urlpatterns = [
> path('', views.myview),
> path('admin/', admin.site.urls),
> ]
>
> }}}
>
> When running the server I get
>
> {{{
> django.core.exceptions.ImproperlyConfigured: The included URLconf
> 'bug.urls' does not appear to have any patterns in it. If you see valid
> patterns in the file then the issue is probably caused by a circular
> import.
> }}}
>
> When in fact I expect it to say
> {{{
>   File "/home/ariel-nt/Desktop/test/bug/bugtest/views.py", line 6, in
> 
> raise MyCustomExceptionShadowed('I have a description of your error')
> bugtest.views.MyCustomExceptionShadowed: I have a description of your
> error
> }}}
>
> I tested this with django 2.1 and it works as expected, so I'll now try
> to find the root cause of the error and give an update here

New description:

 The new version of django somehow captures all the exceptions ocurred
 while parsing the urlpatterns.

 How to reproduce:
   * Create a django project
   * Create a an app

 app/views.py
 {{{
 from django.shortcuts import render

 class MyCustomExceptionShadowed(Exception):
   pass

 raise MyCustomExceptionShadowed('I have a description of your error')

 # Create your views here.
 def myview(request):
   pass
 }}}

 urls.py
 {{{
 from django.contrib import admin
 from django.urls import path

 from bugtest import views

 urlpatterns = [
 path('', views.myview),
 path('admin/', admin.site.urls),
 ]

 }}}

 When running the server I get

 {{{
 django.core.exceptions.ImproperlyConfigured: The included URLconf
 'bug.urls' does not appear to have any patterns in it. If you see valid
 patterns in the file then the issue is probably caused by a circular
 import.
 }}}

 When in fact I expect it to say
 {{{
   File "/home/ariel-nt/Desktop/test/bug/bugtest/views.py", line 6, in
 
 raise MyCustomExceptionShadowed('I have a description of your error')
 bugtest.views.MyCustomExceptionShadowed: I have a description of your
 error
 }}}

 I tested this with django 2.1 and it works as expected, so I'll now try to
 find the root cause of the error and give an update here
 The issue in introduced in this commit
 
[https://github.com/django/django/commit/097457afe47e50e76d53b1cd3312ba8364f866cb
 #diff-46e69f287173eef41fcbfeba05501954R274]
 This line
 
[https://github.com/django/django/blob/097457afe47e50e76d53b1cd3312ba8364f866cb/django/utils/autoreload.py#L274]
 absorbs all the exceptions not showing them to the developer.

--

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

[Django] #30728: Django urls patterns resolver shadowing exceptions thrown everywhere else

[Django]

#30728: Django urls patterns resolver shadowing exceptions thrown everywhere 
else
---+
   Reporter:  maks500  |  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  Core (URLs)  |Version:  2.2
   Severity:  Normal   |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 The new version of django somehow captures all the exceptions ocurred
 while parsing the urlpatterns.

 How to reproduce:
   * Create a django project
   * Create a an app

 app/views.py
 {{{
 from django.shortcuts import render

 class MyCustomExceptionShadowed(Exception):
   pass

 raise MyCustomExceptionShadowed('I have a description of your error')

 # Create your views here.
 def myview(request):
   pass
 }}}

 urls.py
 {{{
 from django.contrib import admin
 from django.urls import path

 from bugtest import views

 urlpatterns = [
 path('', views.myview),
 path('admin/', admin.site.urls),
 ]

 }}}

 When running the server I get

 {{{
 django.core.exceptions.ImproperlyConfigured: The included URLconf
 'bug.urls' does not appear to have any patterns in it. If you see valid
 patterns in the file then the issue is probably caused by a circular
 import.
 }}}

 When in fact I expect it to say
 {{{
   File "/home/ariel-nt/Desktop/test/bug/bugtest/views.py", line 6, in
 
 raise MyCustomExceptionShadowed('I have a description of your error')
 bugtest.views.MyCustomExceptionShadowed: I have a description of your
 error
 }}}

 I tested this with django 2.1 and it works as expected, so I'll now try to
 find the root cause of the error and give an update here

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

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

Re: [Django] #30727: Pickling a Query object evaluates querysets in Subquery expressions

[Django]

#30727: Pickling a Query object evaluates querysets in Subquery expressions
-+-
 Reporter:  Andrew Brown |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Andrew Brown):

 * type:  Uncategorized => 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 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.91d623245bb27d1af90de06f291afed5%40djangoproject.com.

Re: [Django] #30727: Pickling a Query object evaluates querysets in Subquery expressions

[Django]

#30727: Pickling a Query object evaluates querysets in Subquery expressions
-+-
 Reporter:  Andrew Brown |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Andrew Brown):

 * has_patch:  0 => 1


Comment:

 PR: https://github.com/django/django/pull/11707

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

[Django] #30727: Pickling a Query object evaluates querysets in Subquery expressions

[Django]

#30727: Pickling a Query object evaluates querysets in Subquery expressions
-+-
   Reporter:  Andrew |  Owner:  nobody
  Brown  |
   Type: | Status:  new
  Uncategorized  |
  Component:  Database   |Version:  2.2
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I wrote a test case for `tests/queryset_pickle/tests.py` modeled after the
 test from bug #27499 which is very similar.

 {{{#!python
 def test_pickle_subquery_queryset_not_evaluated(self):
 """
 Verifies that querysets passed into Subquery expressions
 are not evaluated when pickled
 """
 groups = Group.objects.annotate(
 has_event=models.Exists(Event.objects.filter(group_id=models.OuterRef('id')))
 )
 with self.assertNumQueries(0):
 pickle.loads(pickle.dumps(groups.query))
 }}}

 The Subquery class (which is the base for `Exists`) only stores the
 underlying query object and throws the QuerySet away (as of this
 
[https://github.com/django/django/commit/96b6ad94d9ebbd57b77b44e185ee215b5b899ac8
 commit], although I don't think it worked before that). So in theory it
 shouldn't be pickling the QuerySet.

 However, the QuerySet is still stored on the instance within the
 `_constructor_args` attribute added by the `@deconstructible` decorator on
 the `BaseExpression` base class. So when the inner query object gets
 pickled, so does the QuerySet, which attempts to evaluate it. In this
 case, it gets the error "ValueError: This queryset contains a reference to
 an outer query and may only be used in a subquery." since the inner
 queryset is being evaluated independently when called from pickle: it
 calls `QuerySet.__getstate__()`.

 I'm not sure what the best solution is here. I made a patch that adds the
 following override to `__getstate__` to the SubQuery class, which fixes
 the problem and passes all other Django tests on my machine. I'll submit a
 PR shortly, but welcome any better approaches since I'm not sure what else
 that may effect.

 {{{#!python
 class Subquery(Expression):
 ...
 def __getstate__(self):
 obj_dict = super().__getstate__()
 obj_dict.pop('_constructor_args', None)
 return obj_dict
 }}}

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

Re: [Django] #30726: 'week' queryset returns no objects

[Django]

#30726: 'week' queryset returns no objects
-+-
 Reporter:  recvfrom |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 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 Nasir Hussain):

 * has_patch:  0 => 1
 * type:  Uncategorized => Bug
 * 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/066.35abb249df699cbc77290c72c4c33ff3%40djangoproject.com.

Re: [Django] #30726: 'week' queryset returns no objects

[Django]

#30726: 'week' queryset returns no objects
-+-
 Reporter:  recvfrom |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 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 Nasir Hussain):

 Looks like its fixed in master branch by this
 
[https://github.com/django/django/commit/cef3f2d3c64055c9fc1757fd61dba24b557a2add
 commit] which is part of #28373. We might need to take that fix to 2.2.5
 too.

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

[Django] #30726: 'week' queryset returns no objects

[Django]

#30726: 'week' queryset returns no objects
-+-
   Reporter:  recvfrom   |  Owner:  nobody
   Type: | Status:  new
  Uncategorized  |
  Component:  Database   |Version:  2.2
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Using the 'week' queryset modifier results in no objects being returned,
 despite there being objects in the database.  Here's a simplified version
 of the model being used:

 {{{
 import datetime
 import pytz

 def timestamp():
 return pytz.utc.localize(datetime.datetime.utcnow())

 class ReportConfig(models.Model):
 last_modified = models.DateTimeField(default=timestamp)
 }}}

 From the shell:

 {{{
 In [54]: ReportConfig.objects.count()
 Out[54]: 853

 In [55]:
 
ReportConfig.objects.filter(last_modified__week__gte=0,last_modified__week__lte=53).count()
 Out[55]: 0

 In [56]: ReportConfig.objects.filter(last_modified__week=34).count()
 Out[56]: 0

 In [57]: ReportConfig.objects.last().last_modified.isocalendar()[1]
 Out[57]: 34
 }}}

 I'm using Django 2.2.4 and MySQL Server version: 5.7.25-log

-- 
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/051.f3715cf25fbbd108ce7b6c10d2f48642%40djangoproject.com.

Re: [Django] #30439: ngettext broken for certain locales due to catalog merging

[Django]

#30439: ngettext broken for certain locales due to catalog merging
-+-
 Reporter:  Michal Čihař |Owner:  Claude
 |  Paroz
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  2.2
  Internationalization   |
 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 Claude Paroz):

 No, this is unrelated. You probably don't have `django.contrib.postgres`
 in your `INSTALLED_APPS`.

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

Re: [Django] #30722: Rate-limit autocomplete widgets Ajax requests

[Django]

#30722: Rate-limit autocomplete widgets Ajax requests
-+-
 Reporter:  Federico Jaramillo   |Owner:  Federico
  Martínez   |  Jaramillo Martínez
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  master
 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 Federico Jaramillo Martínez):

 * needs_better_patch:  1 => 0


Comment:

 Updated the patch, tests are passing.

 500 was the number that gave me the least amount of unnecessary requests
 while still giving a perception of responsiveness, but those were more or
 less empiric tests with some co-workers. More than 500 **felt** slow.

 We found that less than 250 would start sending requests for slow typers.

 Given that this would be a default, I proposed 500 as that was the higher
 acceptable number for us. If a specific site requires a lower delay, it
 can be overridden on a custom widget or by overriding
 `resources/static/admin/js/autocomplete.js`.

 I thought that it would be more important to avoid unnecessary requests
 over the gain of 100ms in the admin area.

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

Re: [Django] #30573: Don't assume that things are "easy"/"obvious"/"simple" in the docs.

[Django]

#30573: Don't assume that things are "easy"/"obvious"/"simple" in the docs.
-+-
 Reporter:  Tobias Kunze |Owner:  Tobias
 Type:   |  Kunze
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 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 felixxm):

 * owner:  nobody => Tobias Kunze


Comment:

 Fix is already submitted, you should rather search for tickets without
 patches and owners.

-- 
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/062.a5acbae7f1b7791107c0b327d17a60f3%40djangoproject.com.

Re: [Django] #30725: Textbox size of a DateTimeField becomes too small in admin.TabularInline when browser windows is made smaller

[Django]

#30725: Textbox size of a DateTimeField becomes too small in admin.TabularInline
when browser windows is made smaller
-+
 Reporter:  Basil Eric Rabi  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  2.2
 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:  1
-+

Comment (by felixxm):

 Feel-free (I saw that you left the same question in few tickets) it's
 probably better to focus on 1-2 tickets and start to work on others when
 fix is ready.

-- 
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/067.5c0be03d822f5e584438d4e14d9f614b%40djangoproject.com.

Re: [Django] #29336: No docs for circular inheritance

[Django]

#29336: No docs for circular inheritance
-+-
 Reporter:  Adrian Turjak|Owner:  Adrian
 Type:   |  Turjak
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by felixxm):

 I don't think that there is a need to reassign this ticket, discussion is
 in progress.

 Replying to [comment:3 Tapasweni Pathak]:
 > Hello folks: Can I take the ticket?

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

Re: [Django] #30439: ngettext broken for certain locales due to catalog merging

[Django]

#30439: ngettext broken for certain locales due to catalog merging
-+-
 Reporter:  Michal Čihař |Owner:  Claude
 |  Paroz
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  2.2
  Internationalization   |
 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 Helder Correia):

 Strings from django.contrib.postgres are not being translated. Is this the
 same issue?

 {{{
 #!python
 >>> from django.utils.translation import activate, gettext as _
 >>> activate('pt')
 >>> _('The start of the range must not exceed the end of the range.')  #
 django/contrib/postgres/forms/ranges.py:20
 'The start of the range must not exceed the end of the range.'
 >>> _('This field cannot be null.')  #
 django/db/models/fields/__init__.py:105
 'Este campo não pode ser nulo.'
 }}}

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

Re: [Django] #28622: Allow password reset token to expire in under a day

[Django]

#28622: Allow password reset token to expire in under a day
-+-
 Reporter:  Nijamudeen   |Owner:  Hasan
 Type:   |  Ramezani
  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:  0|UI/UX:  0
-+-
Changes (by Hasan Ramezani):

 * owner:  Zach Liu => Hasan Ramezani
 * needs_docs:  1 => 0


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

Re: [Django] #30296: Add how-to guide for JavaScript frameworks integration

[Django]

#30296: Add how-to guide for JavaScript frameworks integration
-+-
 Reporter:  Maciej Olko  |Owner:  Josef
 |  Rousek
 Type:  New feature  |   Status:  assigned
Component:  Documentation|  Version:
 Severity:  Normal   |   Resolution:
 Keywords:  javascript, rest,| Triage Stage:  Accepted
  api, assets|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Josef Rousek):

 Replying to [comment:3 tapaswenipathak]:
 > Hello folks: Can I take the ticket or the ticket is for internal folks?

 Hi there. Feel free to take it. I created a repo with basic guide, but
 haven't got back. https://github.com/stlk/django-webpack

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

Re: [Django] #30711: Document django.contrib.postgres.fields.hstore.KeyTransform.

[Django]

#30711: Document django.contrib.postgres.fields.hstore.KeyTransform.
-+-
 Reporter:  Gustav Eiman |Owner:
 Type:   |  tapaswenipathak
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  HStoreField F| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Gustav Eiman):

 * owner:  nobody => tapaswenipathak
 * status:  new => assigned


Comment:

 Replying to [comment:4 tapaswenipathak]:
 > Hello folks: Can I take the ticket?
 That would be great! I'll assign it to you.

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

Re: [Django] #30255: docutils reports an error rendering view docstring when the first line is not empty

[Django]

#30255: docutils reports an error rendering view docstring when the first line 
is
not empty
---+
 Reporter:  Manlio Perillo |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admindocs  |  Version:  2.1
 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 tapaswenipathak):

 Hello folks: Can I 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/065.89d017b0878fab96183aa3774f3e3795%40djangoproject.com.

Re: [Django] #30296: Add how-to guide for JavaScript frameworks integration

[Django]

#30296: Add how-to guide for JavaScript frameworks integration
-+-
 Reporter:  Maciej Olko  |Owner:  Josef
 |  Rousek
 Type:  New feature  |   Status:  assigned
Component:  Documentation|  Version:
 Severity:  Normal   |   Resolution:
 Keywords:  javascript, rest,| Triage Stage:  Accepted
  api, assets|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by tapaswenipathak):

 Hello folks: Can I take the ticket or the ticket is for internal folks?

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

Re: [Django] #30573: Don't assume that things are "easy"/"obvious"/"simple" in the docs.

[Django]

#30573: Don't assume that things are "easy"/"obvious"/"simple" in the docs.
--+
 Reporter:  Tobias Kunze  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 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
--+

Comment (by tapaswenipathak):

 Hello folks: I would like PRing for the ticket? Is the PR merged?

-- 
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/062.6dc58b3bbc77acac9281d3f4f57773a8%40djangoproject.com.

Re: [Django] #30597: Improve documentation on reseting an app's migrations to zero.

[Django]

#30597: Improve documentation on reseting an app's migrations to zero.
--+
 Reporter:  Keryn Knight  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 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 tapaswenipathak):

 Hi folks: Can I 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/067.a0fdaeaec276103529dbce138121dbb1%40djangoproject.com.

Re: [Django] #30711: Document django.contrib.postgres.fields.hstore.KeyTransform.

[Django]

#30711: Document django.contrib.postgres.fields.hstore.KeyTransform.
--+
 Reporter:  Gustav Eiman  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  HStoreField F | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by tapaswenipathak):

 Hello folks: Can I take the ticket?

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

Re: [Django] #30725: Textbox size of a DateTimeField becomes too small in admin.TabularInline when browser windows is made smaller

[Django]

#30725: Textbox size of a DateTimeField becomes too small in admin.TabularInline
when browser windows is made smaller
---+
 Reporter:  basilrabi  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  2.2
 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:  1
---+

Comment (by tapaswenipathak):

 Hello folks: Can I take the ticket?

-- 
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/067.8f550189a98b2ffbd2bd67e0afda89b1%40djangoproject.com.

Re: [Django] #28290: Doc sections are missing target (labels) links

[Django]

#28290: Doc sections are missing target (labels) links
-+-
 Reporter:  Tony Narlock |Owner:  Kees Hink
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  docs labels  | Triage Stage:  Accepted
  intersphinx|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by tapaswenipathak):

 Hello folks: Can I take the ticket?

-- 
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/062.4418be9a78a8a3e83b1df4daed3936d8%40djangoproject.com.

Re: [Django] #29336: No docs for circular inheritance

[Django]

#29336: No docs for circular inheritance
-+-
 Reporter:  Adrian Turjak|Owner:  Adrian
 Type:   |  Turjak
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by tapaswenipathak):

 Hello folks: Can I take the ticket?

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

Re: [Django] #30064: Admin search with a null character crashes with "A string literal cannot contain NUL (0x00) characters." on PostgreSQL

[Django]

#30064: Admin search with a null character crashes with "A string literal cannot
contain NUL (0x00) characters." on PostgreSQL
-+-
 Reporter:  kenichi-cc   |Owner:  Can
 |  Sarıgöl
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  2.1
 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 Can Sarıgöl):

 no problem at all, the important thing was to solve the problem :)

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

Re: [Django] #30507: Update admin's jQuery to 3.4.X.

[Django]

#30507: Update admin's jQuery to 3.4.X.
-+-
 Reporter:  felixxm  |Owner:
 Type:   |  dulmandakh
  Cleanup/optimization   |   Status:  closed
Component:  contrib.admin|  Version:  master
 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 Mariusz Felisiak ):

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


Comment:

 In [changeset:"06372a8d274d5a03f72078180ea355b9c7434fb1" 06372a8d]:
 {{{
 #!CommitTicketReference repository=""
 revision="06372a8d274d5a03f72078180ea355b9c7434fb1"
 Fixed #30507 -- Updated admin's jQuery to 3.4.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.e8987835da3973e039a2f60bc3e5f90b%40djangoproject.com.

Re: [Django] #30064: Admin search with a null character crashes with "A string literal cannot contain NUL (0x00) characters." on PostgreSQL

[Django]

#30064: Admin search with a null character crashes with "A string literal cannot
contain NUL (0x00) characters." on PostgreSQL
-+-
 Reporter:  kenichi-cc   |Owner:  Can
 |  Sarıgöl
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  2.1
 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 Carlton Gibson):

 The commit here 5b4c6b58a097028de970875605680df941ab0a47 has been
 incorrectly credited to me.

 It was the work of Can Sarıgöl. My apologies Can!


 (I **think**, with input from Mariusz, that merging via the GitHub UI
 after pushing edits can, in circumstances yet to be 100% clarified, result
 in this kind of error. Will use the CLI in these cases.)

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

Re: [Django] #25367: Allow expressions in .filter() calls

[Django]

#25367: Allow expressions in .filter() calls
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Matthew
 Type:   |  Schinckel
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 felixxm):

 * needs_better_patch:  1 => 0


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

Re: [Django] #30715: ArrayField lookups crash on ArrayAgg() over AutoFields.

[Django]

#30715: ArrayField lookups crash on ArrayAgg() over AutoFields.
-+-
 Reporter:  NyanKiyoshi  |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  array, serial,   | Triage Stage:  Ready for
  postgres, psql, auto, id   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson ):

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


Comment:

 In [changeset:"521308e575e4510ef4256f2ba2943a5e570c9328" 521308e5]:
 {{{
 #!CommitTicketReference repository=""
 revision="521308e575e4510ef4256f2ba2943a5e570c9328"
 Fixed #30715 -- Fixed crash of ArrayField lookups on ArrayAgg annotations
 over AutoField.
 }}}

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

Re: [Django] #30715: ArrayField lookups crash on ArrayAgg() over AutoFields.

[Django]

#30715: ArrayField lookups crash on ArrayAgg() over AutoFields.
-+-
 Reporter:  NyanKiyoshi  |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  array, serial,   | Triage Stage:  Ready for
  postgres, psql, auto, id   |  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/069.29777f12b9edc1a0351f45c8864f9749%40djangoproject.com.

Re: [Django] #30725: Textbox size of a DateTimeField becomes too small in admin.TabularInline when browser windows is made smaller

[Django]

#30725: Textbox size of a DateTimeField becomes too small in admin.TabularInline
when browser windows is made smaller
---+
 Reporter:  basilrabi  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  2.2
 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:  1
---+
Changes (by Carlton Gibson):

 * easy:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 OK, yes. Looks like a CSS adjustment (`min-width`?) is needed. Thanks for
 the report (and screenshot!)

-- 
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/067.31d6ceb78ebf080a8b06cd21f3e87e4a%40djangoproject.com.

Re: [Django] #30591: MySQL: 1215 - "Cannot add foreign key constraint" when altering type of unique field referenced by ForeignKey.

[Django]

#30591: MySQL: 1215 - "Cannot add foreign key constraint" when altering type of
unique field referenced by ForeignKey.
--+--
 Reporter:  Cornelis Poppema  |Owner:  Adnan Umer
 Type:  Bug   |   Status:  assigned
Component:  Migrations|  Version:  master
 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
--+--
Changes (by felixxm):

 * 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/066.3941c98b67527d2c6b9ca8d3ea93df72%40djangoproject.com.

Re: [Django] #30720: Allow specifying multiple domains for makemessages command. (was: allow specifying multiple domains for makemessages and compilemessages commands)

[Django]

#30720: Allow specifying multiple domains for makemessages command.
-+-
 Reporter:  c v t|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:  wontfix
 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 felixxm):

 * status:  new => closed
 * version:  2.2 => master
 * resolution:   => wontfix
 * easy:  1 => 0


Comment:

 Thanks for this ticket.

 `compilemessages` doesn't have `domain` argument.

 Supporting multiple domains in `makemessages` can still be clunky, because
 they handle different extensions etc. It's probably not worth to add a
 complexity here.
 Closing for now, nevertheless, if you would like to provide a patch we can
 evaluate it and reopen the ticket if consensus is reached.

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