[Django] #27526: test_fuzzy_compiling failing on a machine with 64 cores

[Django]

#27526: test_fuzzy_compiling failing on a machine with 64 cores
+
   Reporter:  Raphaël Hertzog   |  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  Internationalization  |Version:  1.10
   Severity:  Release blocker   |   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 Hello,

 in Debian we recently got a bugreport which essentially boils down to a
 test suite failure when run with default parallel option on a machine with
 64 cores and the failing test is this one:
 {{{
 ==
 FAIL: test_fuzzy_compiling (i18n.test_compilation.FuzzyTranslationTest)
 --
 Traceback (most recent call last):
   File "/usr/lib/python2.7/unittest/case.py", line 329, in run
 testMethod()
   File "/<>/tests/i18n/test_compilation.py", line 218, in
 test_fuzzy_compiling
 self.assertEqual(ugettext('Lenin'), force_text('Ленин'))
   File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
 assertion_func(first, second, msg=msg)
   File "/usr/lib/python2.7/unittest/case.py", line 924, in
 assertMultiLineEqual
 self.fail(self._formatMessage(msg, standardMsg))
   File "/usr/lib/python2.7/unittest/case.py", line 410, in fail
 raise self.failureException(msg)
 AssertionError: u'Lenin' != u'\u041b\u0435\u043d\u0438\u043d'
 - Lenin
 + \u041b\u0435\u043d\u0438\u043d
 }}}

 The original bug report is here: https://bugs.debian.org/844139
 The test was run on a big Amazon EC2 instance (not sure which one exactly)
 if you want to try to reproduce it.

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

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

[Django] #27525: Revert to previous migration automatically after failure when using MySQL backend

[Django]

#27525: Revert to previous migration automatically after failure when using 
MySQL
backend
-+-
   Reporter:  Sandy  |  Owner:  nobody
  Agafonoff  |
   Type: | Status:  new
  Cleanup/optimization   |
  Component: |Version:  1.10
  Migrations |   Keywords:  migrations, mysql,
   Severity:  Normal |  revert
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Owing to the fact MySQL does not support transactional DDL, would it be
 possible to automatically migrate to the previous migration, rather than
 leave the database in an inconsistent state?

 Obviously, not all statements in a migration can be reversed, and,
 reverting to the previous migration is currently the developers decision,
 however in a cloud based CI/CD, automatic deployment based environment,
 allowing this to be run without human intervention would be a plus.

 Possibly a flag on the migrate command like --fail-revert, or possibly a
 field in the migration class would be best, so I can decide on a per-
 migration basis the behaviour I would intend.

 I understand this is going to be a niche request, however, I would like to
 open a discussion to see if there is some merit 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/051.9c65ffe2d8e260d07782a70cfa860e00%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26920: GEOSGeometry objects compare equal despite different SRID

[Django]

#26920: GEOSGeometry objects compare equal despite different SRID
-+-
 Reporter:  Raphael Das Gupta|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  geodjango, equality  | 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 Tim Graham):

 * stage:  Accepted => Ready for checkin


Comment:

 Looks good, pending a +1 from a GIS expert.

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

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

Re: [Django] #27506: HttpRequest.build_absolute_uri throws DisallowedHost

[Django]

#27506: HttpRequest.build_absolute_uri throws DisallowedHost
-+-
 Reporter:  Daniel Hahler|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  HTTP handling|  Version:  1.10
 Severity:  Normal   |   Resolution:  invalid
 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 Daniel Hahler):

 Makes total sense now - thanks for the explanation.

 I've found `get_raw_uri` also (just above!), and created a PR to fix it
 for Opbeat: https://github.com/opbeat/opbeat_python/pull/143.

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

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

Re: [Django] #16682: KeyboardInterrupt not handled properly in transaction aborting

[Django]

#16682: KeyboardInterrupt not handled properly in transaction aborting
-+-
 Reporter:  Malcolm Tredinnick   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  1.11 | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by felixxm):

 I wasn't able to reproduce the hang on Oracle 11g/12c. I will try later
 with Oracle DB Developer VM. Small suggestion is to use `signal.SIGINT`
 instead of signal number.

 {{{#!python
 --- a/tests/transactions/tests.py
 +++ b/tests/transactions/tests.py
 @@ -1,6 +1,7 @@
  from __future__ import unicode_literals

  import os
 +import signal
  import sys
  import threading
  import time
 @@ -225,8 +226,8 @@ class AtomicTests(TransactionTestCase):
  with transaction.atomic():
  Reporter.objects.create(first_name='Tintin')
  # Send SIGINT (simulate Ctrl-C). One call isn't enough.
 -os.kill(os.getpid(), 2)
 -os.kill(os.getpid(), 2)
 +os.kill(os.getpid(), signal.SIGINT)
 +os.kill(os.getpid(), signal.SIGINT)
  except KeyboardInterrupt:
  pass
  self.assertEqual(Reporter.objects.all().count(), 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.ecababa58618bb8f406bdbbff716%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27470: CSRF context processor never sets NOTPROVIDED

[Django]

#27470: CSRF context processor never sets NOTPROVIDED
---+--
 Reporter:  Nick Sandford  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  CSRF   |  Version:  1.10
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Tim Graham):

 Nick, could you give more specific steps to reproduce the issue? For
 example, what does "if the 404 handler is called from a URL that doesn't
 exist" look like?

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

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

Re: [Django] #26543: Changelist actions don't redirect after failed action resulting in possible ERR_CACHE_MISS in next steps

[Django]

#26543: Changelist actions don't redirect after failed action resulting in 
possible
ERR_CACHE_MISS in next steps
-+-
 Reporter:  Emmanuelle   |Owner:  Adonys
  Delescolle |  Alea Boffill
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  1.9
 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:  1
-+-
Changes (by Adonys Alea Boffill):

 * status:  new => assigned
 * owner:  nobody => Adonys Alea Boffill


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

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

Re: [Django] #27510: Allow custom keyword arguments to modelform_factory in ModelFormMixin

[Django]

#27510: Allow custom keyword arguments to modelform_factory in ModelFormMixin
---+-
 Reporter:  Tom|Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Generic views  |  Version:  1.10
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Someday/Maybe
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by Tim Graham):

 * stage:  Unreviewed => Someday/Maybe


Comment:

 Moving to Someday/Maybe pending mailing list discussion.

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

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

Re: [Django] #27465: Allow EmailMessage to load attachments from the Storage API (was: Allow EmailMessage(attachments=[...]) to load from the filesystem)

[Django]

#27465: Allow EmailMessage to load attachments from the Storage API
+
 Reporter:  Thomas Güttler  |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  Core (Mail) |  Version:  1.10
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by Tim Graham):

 * 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.16c923fcdf8016b8f0b119c788f66a6d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27521: QueryDict is inconsistently converted to kwargs between CPython and PyPy

[Django]

#27521: QueryDict is inconsistently converted to kwargs between CPython and PyPy
-+-
 Reporter:  Mark Heppner |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:  1.10
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  PyPy QueryDict   | Triage Stage:
  MultiValueDict |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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


Comment:

 Okay, I'd suggest to file a bug with PyPy and reopen this ticket if they
 indicate that Django is at fault. Thanks.

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

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

Re: [Django] #27524: Using user instance (instead of get_user_model()) leads to errors when user model is overridden

[Django]

#27524: Using user instance (instead of get_user_model()) leads to errors when 
user
model is overridden
--+--
 Reporter:  Andy Martin   |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.auth  |  Version:  1.8
 Severity:  Normal|   Resolution:  wontfix
 Keywords:| Triage Stage:  Unreviewed
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by Tim Graham):

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


Comment:

 Agreed, I don't think it's feasible to support a different API and give it
 complete test coverage.

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

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

Re: [Django] #27498: Filtering annotated field in SQLite returns wrong results

[Django]

#27498: Filtering annotated field in SQLite returns wrong results
-+-
 Reporter:  Tim Düllmann |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  sqlite,  | Triage Stage:  Accepted
  annotations, filter|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * stage:  Unreviewed => Accepted


Comment:

 Reproduced at b1a9041535db5d03dab7f205669f0ab7a47de854.

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

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

Re: [Django] #27524: Using user instance (instead of get_user_model()) leads to errors when user model is overridden

[Django]

#27524: Using user instance (instead of get_user_model()) leads to errors when 
user
model is overridden
--+--
 Reporter:  Andy Martin   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by Simon Charette):

 Hello Andy,

 There's many occurrences of access to `instance._meta` through Django's
 code base where it's assumed to return the same value as
 `instance.__class__._meta`. In order to prevent breakages I think it
 should be fixed in the library you use to expose `_meta` API compliant
 objects.

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

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

Re: [Django] #26570: Test runner imports models package with Python 3.5+

[Django]

#26570: Test runner imports models package with Python 3.5+
---+--
 Reporter:  Torsten Bronger|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.9
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Tim Graham):

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


Comment:

 I don't know enough to determine if this is something we should/can fix in
 Django. I think someone with the use case will have to provide a patch.

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

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

Re: [Django] #27521: QueryDict is inconsistently converted to kwargs between CPython and PyPy

[Django]

#27521: QueryDict is inconsistently converted to kwargs between CPython and PyPy
-+-
 Reporter:  Mark Heppner |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  PyPy QueryDict   | Triage Stage:
  MultiValueDict |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mark Heppner):

 Replying to [comment:1 Tim Graham]:
 > Can you elaborate why Django is at fault (rather than say, PyPy) and/or
 propose a patch?

 I'm not entirely sure what's going on with the internals of converting it
 to kwargs, so I cannot propose a patch nor am I sure if Django is even at
 fault.

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

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

Re: [Django] #27460: Allow declaring a GenericRelation from an abstract model to another abstract model (was: GenericRelation doesn't work from AbstractClass to AbstractClass in Django 1.10(.3))

[Django]

#27460: Allow declaring a GenericRelation from an abstract model to another
abstract model
-+-
 Reporter:  Wolfgang Grim|Owner:  Alex Hill
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  GenericRelation, | Triage Stage:  Accepted
  Abstract, ContentFramework |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * type:  Bug => New feature
 * component:  Core (Other) => Database layer (models, ORM)
 * stage:  Unreviewed => Accepted


Comment:

 Tentatively accepting and retitling based on a skim of the 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.924eeeaf95da584eaa5d44631a68ae31%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #16682: KeyboardInterrupt not handled properly in transaction aborting

[Django]

#16682: KeyboardInterrupt not handled properly in transaction aborting
-+-
 Reporter:  Malcolm Tredinnick   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  1.11 | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * cc: felixxm (added)


Comment:

 Mariusz, are you able to reproduce the hang on Oracle? Any ideas?

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

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

Re: [Django] #26644: SuspiciousFileOperation when creating a File from a NamedTemporaryFile

[Django]

#26644: SuspiciousFileOperation when creating a File from a NamedTemporaryFile
-+-
 Reporter:  Hugo Osvaldo |Owner:  Hugo
  Barrera|  Osvaldo Barrera
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  File,| Triage Stage:  Accepted
  SuspiciousFileOperation,   |
  NamedTemporaryFile, regression |
  1.10   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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


Comment:

 Closing since a patch hasn't been provided and there haven't been reports
 of anyone else hitting the issue. Hugo, feel free to reopen if you want to
 provide a patch.

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

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

Re: [Django] #27518: HTTP Referer leaks password reset link

[Django]

#27518: HTTP Referer leaks password reset link
-+-
 Reporter:  Romain Garrigues |Owner:  Romain
 Type:   |  Garrigues
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.auth |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  password reset   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 Typically we don't add or change behavior of deprecated things.

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

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

Re: [Django] #27522: ./manage runserver --nostatic doesn't return a traceback

[Django]

#27522: ./manage runserver --nostatic doesn't return a traceback
-+-
 Reporter:  Jeroen van Veen  |Owner:  nobody
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  runserver nostatic   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_tests:  0 => 1


Comment:

 Some tests for `runserver` are in `admin_scripts/tests.py`. It might be
 infeasible to test this (for example,
 fe6ddb837d18bd4e71cd22fc18272d31478b19f2 lacked tests) but it would be
 nice to try.

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

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

Re: [Django] #27477: Use QuerySet.select_for_update() in admin change form to fix race condition

[Django]

#27477: Use QuerySet.select_for_update() in admin change form to fix race 
condition
---+--
 Reporter:  Dave Hall  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  admin  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Tim Graham):

 I don't know if this is correct or if it might have some unintended side
 effects. Is the same issue present in the generic class-based editing
 views, for example?

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

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

Re: [Django] #27483: Add a login_required decorator for AJAX requests (was: check login_required ajax users decorators and superuser decorators)

[Django]

#27483: Add a login_required decorator for AJAX requests
-+-
 Reporter:  Ramin Farajpour  |Owner:  Ramin
  Cami   |  Farajpour Cami
 Type:  New feature  |   Status:  closed
Component:  contrib.auth |  Version:  1.10
 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 Tim Graham):

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


Comment:

 Closing, pending further discussion on the mailing list.

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

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

Re: [Django] #26327: Add JSONB_AGG to contrib.postgres

[Django]

#26327: Add JSONB_AGG to contrib.postgres
-+-
 Reporter:  Tomasz Nowak |Owner:  Mads
 |  Jensen
 Type:  New feature  |   Status:  new
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  JSON postgres| Triage Stage:  Ready for
  aggregate  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * has_patch:  0 => 1
 * 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.65c02e8ebfd6e4fa6d8bd9850796%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27221: Document how to escape a percent symbol in ugettext

[Django]

#27221: Document how to escape a percent symbol in ugettext
-+-
 Reporter:  pgcd |Owner:  Henry
 Type:   |  Dang
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  ugettext percent | 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 Tim Graham ):

 In [changeset:"047a62b3f7ddb4f0a3bd72dce46a47ee4a847273" 047a62b3]:
 {{{
 #!CommitTicketReference repository=""
 revision="047a62b3f7ddb4f0a3bd72dce46a47ee4a847273"
 [1.10.x] Fixed #27221 -- Doc'd how to escape a percent symbol in
 ugettext().

 Backport of b1a9041535db5d03dab7f205669f0ab7a47de854 from master
 }}}

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

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

Re: [Django] #27221: Document how to escape a percent symbol in ugettext

[Django]

#27221: Document how to escape a percent symbol in ugettext
-+-
 Reporter:  pgcd |Owner:  Henry
 Type:   |  Dang
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  ugettext percent | 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 Tim Graham ):

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


Comment:

 In [changeset:"b1a9041535db5d03dab7f205669f0ab7a47de854" b1a90415]:
 {{{
 #!CommitTicketReference repository=""
 revision="b1a9041535db5d03dab7f205669f0ab7a47de854"
 Fixed #27221 -- Doc'd how to escape a percent symbol in ugettext().
 }}}

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

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

Re: [Django] #27524: Using user instance (instead of get_user_model()) leads to errors when user model is overridden

[Django]

#27524: Using user instance (instead of get_user_model()) leads to errors when 
user
model is overridden
--+--
 Reporter:  Andy Martin   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by Andy Martin):

 Here's the user model:

 {{{
 from bson import ObjectId
 from mongoengine import Document, StringField, BooleanField, DateTimeField

 class User(Document):
 id = StringField(required=True, primary_key=True, default=lambda:
 str(ObjectId()))
 username = StringField(required=True)
 password = StringField()
 is_active = BooleanField(default=True)
 is_staff = BooleanField(default=False)
 email = StringField()
 first_name = StringField()
 last_name = StringField()
 last_login = DateTimeField()
 }}}

 In our settings.py, we have the following values set:
 {{{
 AUTH_USER_MODEL = 'mongo_auth.MongoUser'
 MONGOENGINE_USER_DOCUMENT = '[...snip...].admin.models.User'  # (points to
 User model defined above)
 }}}

 If you think it should be the responsibility of the person overriding the
 user model to make sure it works fine with Django's contrib.auth
 implementation, that's fine with me, although googling for the error
 message shows other people seem to be hitting the same issue.

 Let me know if you think the use case is valid and, if so, I can look into
 making a regression test.

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

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

Re: [Django] #27437: Can't create GinIndex on ArrayField(CITextField)

[Django]

#27437: Can't create GinIndex on ArrayField(CITextField)
-+-
 Reporter:  Davide Setti |Owner:  Mads
 |  Jensen
 Type:  Bug  |   Status:  assigned
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  postgres, indexes,   | Triage Stage:
  gin, citext, arrays|  Someday/Maybe
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * stage:  Accepted => Someday/Maybe


Comment:

 Yes, this looks a bit specialized. In my opinion, `contrib.postgres`
 should aim for implementing things that are an ~80% use case. As Simon
 said, it would be nice to have more evidence that this is common before
 committing to include it. Anyway, the code is on the pull request for
 anyone who would like to use it in their own 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/061.4da458388bc18947df0edf47f650c58c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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

[Django]

#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Andrey
 Type:   |  Kuzminov
  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:  1|UI/UX:  0
-+-
Changes (by Tim Graham):

 * 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.d1f878808095f81482c61685cbfc2da7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27517: TemplateResponseMixin with charset does not work

[Django]

#27517: TemplateResponseMixin with charset does not work
+
 Reporter:  Kosei Kitahara  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Generic views   |  Version:  1.10
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by Tim Graham):

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


Comment:

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

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

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

Re: [Django] #27250: Confusing assignment with CheckboxSelectMultiple

[Django]

#27250: Confusing  assignment with CheckboxSelectMultiple
-+-
 Reporter:  Daniel Lamprecht |Owner:
 |  MartinArroyo
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
  CheckboxSelectMultiple label   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"abd434059e1aaff35bc848998ad2335c630ba434" abd43405]:
 {{{
 #!CommitTicketReference repository=""
 revision="abd434059e1aaff35bc848998ad2335c630ba434"
 Fixed #27250 -- Removed 'for ="..."' from CheckboxSelectMultiple's
 .
 }}}

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

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

Re: [Django] #25612: django.contrib.auth should include support for 2fa out of the box

[Django]

#25612: django.contrib.auth should include support for 2fa out of the box
--+-
 Reporter:  Alex Gaynor   |Owner:  mlevental
 Type:  New feature   |   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:  0 |UI/UX:  0
--+-

Comment (by Tim Graham):

 It would be better to put together a proposal and and post it on the
 DevelopersMailingList. That reaches a wider audience that the few people
 following 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.11f333da8aad5e655d724b7927ad813e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27524: Using user instance (instead of get_user_model()) leads to errors when user model is overridden

[Django]

#27524: Using user instance (instead of get_user_model()) leads to errors when 
user
model is overridden
--+--
 Reporter:  Andy Martin   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by Tim Graham):

 * component:  Uncategorized => contrib.auth
 * needs_tests:  0 => 1


Comment:

 Could you provide details about your custom user model? I don't know how
 `user._meta` returns `MetaDict`. If the use case is valid, we'll also need
 a regression test. By the way, you don't need to attach a patch to the
 ticket, the [https://github.com/django/django/pull/7597 PR] is enough.

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

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

Re: [Django] #25612: django.contrib.auth should include support for 2fa out of the box

[Django]

#25612: django.contrib.auth should include support for 2fa out of the box
--+-
 Reporter:  Alex Gaynor   |Owner:  mlevental
 Type:  New feature   |   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:  0 |UI/UX:  0
--+-

Comment (by mlevental):

 It should be distinguishable if a user is authenticated with 1 factor or
 2, e.g. for checking if the user is already authenticated with the
 required number of factors so relogging can be omitted. Therefore a field
 like {{{is_two_factor_authenticated}}} can be added to the {{{User}}}
 model.

 But then it would be unclear whether the existing field
 {{{is_authenticated}}} means the user is authenticated with 1 or 2
 factors.
 To find that out one would have to additionally check for the value of
 {{{is_two_factor_authenticated}}} and this would be cumbersome.
 For convenience another field like {{{is_one_factor_authenticated}}} could
 be introduced. And to make {{{is_authenticated}}} behave correctly it
 should return {{{True}}} if either {{{is_one_factor_authenticated}}} or
 {{{is_two_factor_authenticated}}} is {{{True}}}.

 What are your thoughts on that?

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

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

Re: [Django] #27524: Using user instance (instead of get_user_model()) leads to errors when user model is overridden

[Django]

#27524: Using user instance (instead of get_user_model()) leads to errors when 
user
model is overridden
---+--
 Reporter:  Andy Martin|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  1.8
 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 Andy Martin):

 * Attachment "0001-Use-get_user_model-instead-of-user-instance-to-
 call-.patch" added.

 Patch file for proposed fix (will also be submitted as a PR on Github)

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

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

[Django] #27524: Using user instance (instead of get_user_model()) leads to errors when user model is overridden

[Django]

#27524: Using user instance (instead of get_user_model()) leads to errors when 
user
model is overridden
-+
   Reporter:  Andy Martin|  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Uncategorized  |Version:  1.8
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 We've been seeing errors like this on 1.8.16:

 {{{
 File "[...snip...]/django/contrib/auth/__init__.py", line 111, in login
 request.session[SESSION_KEY] = user._meta.pk.value_to_string(user)
 AttributeError: 'MetaDict' object has no attribute 'pk'
 }}}

 We solved them by going through the object returned by get_user_model()
 instead of using the user instance directly. This also matches what's done
 in other parts of the codebase (for example, in
 _get_user_session_key(request)).

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

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

Re: [Django] #27221: Document how to escape a percent symbol in ugettext

[Django]

#27221: Document how to escape a percent symbol in ugettext
-+-
 Reporter:  pgcd |Owner:  Henry
 Type:   |  Dang
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  ugettext percent | 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 Tim Graham):

 * 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.f0e7f87d5dc3398f81e891e4dfe8a2da%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27295: Add a system check to prohibit models that start with an underscore

[Django]

#27295: Add a system check to prohibit models that start with an underscore
-+-
 Reporter:  Victor Porton|Owner:  Quentin
 Type:   |  Fulsher
  Cleanup/optimization   |   Status:  closed
Component:  Core (System |  Version:  1.10
  checks)|
 Severity:  Normal   |   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"f62abfc03da61977bf080163f0a2ef014decd86a" f62abfc]:
 {{{
 #!CommitTicketReference repository=""
 revision="f62abfc03da61977bf080163f0a2ef014decd86a"
 Fixed #27295 -- Added a system check to prohibit model names that start or
 end with an underscore or contain double underscores.
 }}}

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

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

Re: [Django] #9519: Add QuerySet.bulk_delete() that issues only a single SQL query

[Django]

#9519: Add QuerySet.bulk_delete() that issues only a single SQL query
-+-
 Reporter:  Joey Wilhelm |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  database, queryset,  | Triage Stage:  Accepted
  delete |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Marcin Nowak):

 Emitting additional bulk_post/pre_delete signal with queryset instance as
 an `instance` argument will be good enough. Just leave current logic but
 add additional signals. I'd like to connect handler(s) which will delete
 related objects also in bulk. Thank 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.892cb402082ed91acdc5fa5730edb83d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26494: executable flags lost when using an archive as a project/app template

[Django]

#26494: executable flags lost when using an archive as a project/app template
--+
 Reporter:  Jakub Dorňák  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Utilities |  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 Anton Samarchyan):

 * cc: desecho@… (added)
 * has_patch:  0 => 1
 * version:  1.9 => master


Comment:

 Added [https://github.com/django/django/pull/7596 PR]

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

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

Re: [Django] #27517: TemplateResponseMixin with charset does not work (was: TemplateResponseMixin with charset does not worked)

[Django]

#27517: TemplateResponseMixin with charset does not work
+--
 Reporter:  Kosei Kitahara  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Generic views   |  Version:  1.10
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

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

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

Re: [Django] #27522: ./manage runserver --nostatic doesn't return a traceback

[Django]

#27522: ./manage runserver --nostatic doesn't return a traceback
-+-
 Reporter:  Jeroen van Veen  |Owner:  nobody
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  runserver nostatic   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * has_patch:  0 => 1
 * needs_tests:  0 => 1


Old description:

> When running ./manage runserver --nostatic, I expect a traceback to be
> returned when
> a syntax error occurs, and I expect the autoreloader still to be
> available. Instead, the
> runserver command exits like:
>

> {{{
> usage: manage.py runserver [-h] [--version] [-v {0,1,2,3}]
>[--settings SETTINGS] [--pythonpath
> PYTHONPATH]
>[--traceback] [--no-color] [--ipv6]
> [--nothreading]
>[--noreload]
>[addrport]
> manage.py runserver: error: unrecognized arguments: --nostatic
> }}}
>
> Ticket: https://github.com/wearespindle/django/tree/ticket_27522

New description:

 When running `./manage runserver --nostatic`, I expect a traceback to be
 returned when
 a syntax error occurs, and I expect the autoreloader still to be
 available. Instead, the
 runserver command exits like:

 {{{
 usage: manage.py runserver [-h] [--version] [-v {0,1,2,3}]
[--settings SETTINGS] [--pythonpath PYTHONPATH]
[--traceback] [--no-color] [--ipv6]
 [--nothreading]
[--noreload]
[addrport]
 manage.py runserver: error: unrecognized arguments: --nostatic
 }}}

--

Comment:

 [https://github.com/django/django/pull/7595 PR] (currently without 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.284cc977f4f809a34b25117ca9af4187%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23829: Allow customizing the `ping_google` URL

[Django]

#23829: Allow customizing the `ping_google` URL
-+-
 Reporter:  Julian Wachholz  |Owner:  (none)
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.sitemaps |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  sitemaps,| Triage Stage:  Accepted
  ping_google|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Asif Saifuddin Auvi):

 * owner:  Asif Saifuddin Auvi => (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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/061.01e33f18eacb08c7d890972be23f1bbc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27522: ./manage runserver --nostatic doesn't return a traceback

[Django]

#27522: ./manage runserver --nostatic doesn't return a traceback
-+-
 Reporter:  Jeroen van Veen  |Owner:  nobody
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  runserver nostatic   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jeroen van Veen):

 * needs_tests:  1 => 0


Old description:

> When running `./manage runserver --nostatic`, I expect a traceback to be
> returned when
> a syntax error occurs, and I expect the autoreloader still to be
> available. Instead, the
> runserver command exits like:
>
> {{{
> usage: manage.py runserver [-h] [--version] [-v {0,1,2,3}]
>[--settings SETTINGS] [--pythonpath
> PYTHONPATH]
>[--traceback] [--no-color] [--ipv6]
> [--nothreading]
>[--noreload]
>[addrport]
> manage.py runserver: error: unrecognized arguments: --nostatic
> }}}

New description:

 When running ./manage runserver --nostatic, I expect a traceback to be
 returned when
 a syntax error occurs, and I expect the autoreloader still to be
 available. Instead, the
 runserver command exits like:


 {{{
 usage: manage.py runserver [-h] [--version] [-v {0,1,2,3}]
[--settings SETTINGS] [--pythonpath PYTHONPATH]
[--traceback] [--no-color] [--ipv6]
 [--nothreading]
[--noreload]
[addrport]
 manage.py runserver: error: unrecognized arguments: --nostatic
 }}}

 Ticket: https://github.com/wearespindle/django/tree/ticket_27522

--

Comment:

 I'm trying to figure out where this test should be placed.

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

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

Re: [Django] #16859: CSRF Improvements

[Django]

#16859: CSRF Improvements
-+-
 Reporter:  Paul McMillan|Owner:  Paul
 Type:   |  McMillan
  Cleanup/optimization   |   Status:  new
Component:  CSRF |  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 Tim Graham):

 * 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.6683549245ab679329aa8329d04ab749%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27394: template "floatformat" tag throws ValueError for big numbers in Python 3

[Django]

#27394: template "floatformat" tag throws ValueError for big numbers in Python 3
-+
 Reporter:  mateuszf |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.10
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  floatformat python3  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by Tim Graham ):

 In [changeset:"41759c908240409d44fc11d07a562268c81f4bdf" 41759c90]:
 {{{
 #!CommitTicketReference repository=""
 revision="41759c908240409d44fc11d07a562268c81f4bdf"
 Refs #27394 -- Removed @expectedFailure from a floatformat test.
 }}}

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

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

Re: [Django] #27513: Optimize Signal.send a tiny bit

[Django]

#27513: Optimize Signal.send a tiny bit
-+-
 Reporter:  Adam Chainz  |Owner:  Adam
 Type:   |  Chainz
  Cleanup/optimization   |   Status:  closed
Component:  Utilities|  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 Tim Graham ):

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


Comment:

 In [changeset:"22a60f8d0b331bf06c066ccba4eea5bb5e4ac9f2" 22a60f8d]:
 {{{
 #!CommitTicketReference repository=""
 revision="22a60f8d0b331bf06c066ccba4eea5bb5e4ac9f2"
 Fixed #27513 -- Made Signal.send()/send_robust() a tiny bit faster.
 }}}

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

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

Re: [Django] #27181: Sites framework does not normalize domains with trailing "."

[Django]

#27181: Sites framework does not normalize domains with trailing "."
---+
 Reporter:  Ran Benita |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.sites  |  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 Tim Graham):

 * 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.0422c9b65d7da4def615ad491197d16a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27515: Make AuthenticationForm use the username length from the user model

[Django]

#27515: Make AuthenticationForm use the username length from the user model
-+-
 Reporter:  Ramin Farajpour  |Owner:  Ramin
  Cami   |  Farajpour Cami
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.auth |  Version:  1.10
 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 Tim Graham):

 * 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.312dce8e252911414e25f6129e2d488d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27499: Pickling a QuerySet evaluates the querysets given to Prefetch in prefetch_related

[Django]

#27499: Pickling a QuerySet evaluates the querysets given to Prefetch in
prefetch_related
-+-
 Reporter:  Adam Chainz  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  prefetch_related | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * component:  Uncategorized => Database layer (models, ORM)
 * 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.76be8af244f45ae5fe00b6d5be78220c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27521: QueryDict is inconsistently converted to kwargs between CPython and PyPy

[Django]

#27521: QueryDict is inconsistently converted to kwargs between CPython and PyPy
-+-
 Reporter:  Mark Heppner |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  PyPy QueryDict   | Triage Stage:
  MultiValueDict |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 Can you elaborate why Django is at fault (rather than say, PyPy) and/or
 propose a patch?

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

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

Re: [Django] #27522: ./manage runserver --nostatic doesn't return a traceback

[Django]

#27522: ./manage runserver --nostatic doesn't return a traceback
-+-
 Reporter:  Jeroen van Veen  |Owner:  nobody
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  runserver nostatic   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 I can reproduce the problem. Without taking a closer look, I'm not sure
 about the solution. If you could write a test, that would certainly help.

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

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

Re: [Django] #27522: ./manage runserver --nostatic doesn't return a traceback

[Django]

#27522: ./manage runserver --nostatic doesn't return a traceback
-+-
 Reporter:  Jeroen van Veen  |Owner:  nobody
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  runserver nostatic   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jeroen van Veen):

 * version:  1.8 => master


Old description:

> When running ./manage runserver --nostatic, I expect a traceback to be
> returned when
> a syntax error occurs, and I expect the autoreloader still to be
> available. Instead, the
> runserver command exits like:
>

> {{{
> usage: manage.py runserver [-h] [--version] [-v {0,1,2,3}]
>[--settings SETTINGS] [--pythonpath
> PYTHONPATH]
>[--traceback] [--no-color] [--ipv6]
> [--nothreading]
>[--noreload]
>[addrport]
> manage.py runserver: error: unrecognized arguments: --nostatic
> }}}

New description:

 When running ./manage runserver --nostatic, I expect a traceback to be
 returned when
 a syntax error occurs, and I expect the autoreloader still to be
 available. Instead, the
 runserver command exits like:


 {{{
 usage: manage.py runserver [-h] [--version] [-v {0,1,2,3}]
[--settings SETTINGS] [--pythonpath PYTHONPATH]
[--traceback] [--no-color] [--ipv6]
 [--nothreading]
[--noreload]
[addrport]
 manage.py runserver: error: unrecognized arguments: --nostatic
 }}}

 Ticket: https://github.com/wearespindle/django/tree/ticket_27522

--

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

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

Re: [Django] #27523: Sitemap ping_google function reverse broken on Django 1.10

[Django]

#27523: Sitemap ping_google function reverse broken on Django 1.10
--+---
 Reporter:  Adam Chainz   |Owner:  Adam Chainz
 Type:  Bug   |   Status:  closed
Component:  contrib.sitemaps  |  Version:  1.10
 Severity:  Normal|   Resolution:  invalid
 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 Adam Chainz):

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


Comment:

 Ok this isn't actually a problem, the Sitemap framework tells you to set
 `name` to the dotted path (and always has):
 https://docs.djangoproject.com/en/1.10/ref/contrib/sitemaps/#initialization

 It's just our urlconf didn't, and this worked via the pre-1.10 `reverse()`
 of dotted paths behaviour.

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

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

Re: [Django] #27518: HTTP Referer leaks password reset link

[Django]

#27518: HTTP Referer leaks password reset link
-+-
 Reporter:  Romain Garrigues |Owner:  Romain
 Type:   |  Garrigues
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.auth |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  password reset   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Romain Garrigues):

 Hi @Florian!

 I get the idea and definitely motivated to try!!
 I guess we should update the CBV **and** the FBV version (even if
 deprecated), and add tests for both?

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

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

Re: [Django] #27518: HTTP Referer leaks password reset link

[Django]

#27518: HTTP Referer leaks password reset link
-+-
 Reporter:  Romain Garrigues |Owner:  Romain
 Type:   |  Garrigues
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.auth |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  password reset   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Florian Apolloner):

 @Romain Garrigues: So what I imagine is the following:

  * The user gets the link: ''/reset/Mq/asdga-yxflkjxc78121/''
  * You store ''asdga-yxflkjxc78121'' in the session and redirect to
 ''/reset/Mq/set-password/'' (luckily our regex allows for this)
  * if the token is ''set-password'' and the session has the proper value
 we can reset the password

 This allows us to:
  * Do not alter the password for the user twice
  * Keep the most compatibility with the existing system (same URL etc, no
 changes needed unless you manually changed the regex)
  * Not leak any information (only Mq which is the user id, which is
 guessable anyways)
  * We do not have to store any extra information in the session

 Is that clear enough? If yes, do you want to try a patch against the class
 based views in master?

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

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

Re: [Django] #27523: Sitemap ping_google function reverse broken on Django 1.10

[Django]

#27523: Sitemap ping_google function reverse broken on Django 1.10
--+---
 Reporter:  Adam Chainz   |Owner:  Adam Chainz
 Type:  Bug   |   Status:  assigned
Component:  contrib.sitemaps  |  Version:  1.10
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+---
Changes (by Adam Chainz):

 * owner:  nobody => Adam Chainz
 * 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.44a3b98fec10e351ced2214658ec1eff%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #27523: Sitemap ping_google function reverse broken on Django 1.10

[Django]

#27523: Sitemap ping_google function reverse broken on Django 1.10
+
   Reporter:  Adam Chainz   |  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  contrib.sitemaps  |Version:  1.10
   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 |
+
 Django 1.10 removed the ability to `reverse()` URLs using a dotted Python
 path, but `ping_google` is left doing so:

 {{{
 if sitemap_url is None:
 try:
 # First, try to get the "index" sitemap URL.
 sitemap_url = reverse('django.contrib.sitemaps.views.index')
 }}}

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

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

Re: [Django] #23829: Allow customizing the `ping_google` URL

[Django]

#23829: Allow customizing the `ping_google` URL
-+-
 Reporter:  Julian Wachholz  |Owner:  Asif
 Type:   |  Saifuddin Auvi
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.sitemaps |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  sitemaps,| Triage Stage:  Accepted
  ping_google|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Adam Chainz):

 * cc: me@… (added)


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

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

Re: [Django] #27506: HttpRequest.build_absolute_uri throws DisallowedHost

[Django]

#27506: HttpRequest.build_absolute_uri throws DisallowedHost
-+-
 Reporter:  Daniel Hahler|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  HTTP handling|  Version:  1.10
 Severity:  Normal   |   Resolution:  invalid
 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 Florian Apolloner):

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


Comment:

 >  I've noticed that using HttpRequest.build_absolute_uri() might throw
 DisallowedHost, which looks like an unexpected side effect.

 I'd call it "works as designed" :D The main idea here is that you need
 `get_host` and `build_absolute_uri` ''usually'' in cases where you are
 sending emails or providing redirect urls for other sites/apis. And those
 are generally the cases where you'd want to ensure that you do not allow
 invalid hosts. So by default this is an important defense line and should
 stay on.

 To allow access to the unvetted URI we've added ''get_raw_uri'' which
 should work in your case -- I am closing the ticket as invalid, please
 reopen if you have any questions there.

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

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

Re: [Django] #27522: ./manage runserver --nostatic doesn't return a traceback

[Django]

#27522: ./manage runserver --nostatic doesn't return a traceback
-+-
 Reporter:  Jeroen van Veen  |Owner:  nobody
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  1.8
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  runserver nostatic   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jeroen van Veen):

 * keywords:   => runserver nostatic


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

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

Re: [Django] #27522: ./manage runserver --nostatic doesn't return a traceback

[Django]

#27522: ./manage runserver --nostatic doesn't return a traceback
-+-
 Reporter:  Jeroen van Veen  |Owner:  nobody
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  1.8
  commands)  |
 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 Jeroen van Veen):

 * version:  1.10 => 1.8


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

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

Re: [Django] #27522: ./manage runserver --nostatic doesn't return a traceback

[Django]

#27522: ./manage runserver --nostatic doesn't return a traceback
-+-
 Reporter:  Jeroen van Veen  |Owner:  nobody
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  1.10
  commands)  |
 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 Jeroen van Veen):

 * 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.0ad2f27ab2ed2dfe8d9b95e4d00967f0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27522: ./manage runserver --nostatic doesn't return a traceback

[Django]

#27522: ./manage runserver --nostatic doesn't return a traceback
-+-
 Reporter:  Jeroen van Veen  |Owner:  nobody
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  1.10
  commands)  |
 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 Jeroen van Veen):

 Please let me know if it needs some more work! :)

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

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

Re: [Django] #27522: ./manage runserver --nostatic doesn't return a traceback

[Django]

#27522: ./manage runserver --nostatic doesn't return a traceback
-+-
 Reporter:  Jeroen van Veen  |Owner:  nobody
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  1.10
  commands)  |
 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 Jeroen van Veen:

Old description:

> When running ./manage runserver --nostatic, I expect a traceback to be
> returned when
> a syntax error occurs, and I expect the autoreloader still to be
> available. Instead, the
> runserver command exits like:
>
> usage: manage.py runserver [-h] [--version] [-v {0,1,2,3}]
>[--settings SETTINGS] [--pythonpath
> PYTHONPATH]
>[--traceback] [--no-color] [--ipv6]
> [--nothreading]
>[--noreload]
>[addrport]
> manage.py runserver: error: unrecognized arguments: --nostatic

New description:

 When running ./manage runserver --nostatic, I expect a traceback to be
 returned when
 a syntax error occurs, and I expect the autoreloader still to be
 available. Instead, the
 runserver command exits like:


 {{{
 usage: manage.py runserver [-h] [--version] [-v {0,1,2,3}]
[--settings SETTINGS] [--pythonpath PYTHONPATH]
[--traceback] [--no-color] [--ipv6]
 [--nothreading]
[--noreload]
[addrport]
 manage.py runserver: error: unrecognized arguments: --nostatic
 }}}

--

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

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

Re: [Django] #27522: ./manage runserver --nostatic doesn't return a traceback

[Django]

#27522: ./manage runserver --nostatic doesn't return a traceback
-+-
 Reporter:  Jeroen van Veen  |Owner:  nobody
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  1.10
  commands)  |
 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 Jeroen van Veen):

 This is a workaround:


 {{{
 --- __init__.py.orig2016-11-22 09:58:38.806209538 +0100
 +++ __init__.py 2016-11-22 09:58:47.656120244 +0100
 @@ -323,6 +323,10 @@
  apps.all_models = defaultdict(OrderedDict)
  apps.app_configs = OrderedDict()
  apps.apps_ready = apps.models_ready = apps.ready =
 True
 +# Execute the runserver command, but strip off
 additional
 +# parameters that cause the argument parser to fail.
 +
 self.fetch_command(subcommand).run_from_argv(self.argv[0:2])
 +return

  # In all other cases, django.setup() is required to succeed.
  else:
 }}}

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

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

[Django] #27522: ./manage runserver --nostatic doesn't return a traceback

[Django]

#27522: ./manage runserver --nostatic doesn't return a traceback
-+-
   Reporter:  Jeroen |  Owner:  nobody
  van Veen   |
   Type:  Bug| Status:  assigned
  Component:  Core   |Version:  1.10
  (Management commands)  |
   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  |
-+-
 When running ./manage runserver --nostatic, I expect a traceback to be
 returned when
 a syntax error occurs, and I expect the autoreloader still to be
 available. Instead, the
 runserver command exits like:

 usage: manage.py runserver [-h] [--version] [-v {0,1,2,3}]
[--settings SETTINGS] [--pythonpath PYTHONPATH]
[--traceback] [--no-color] [--ipv6]
 [--nothreading]
[--noreload]
[addrport]
 manage.py runserver: error: unrecognized arguments: --nostatic

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

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