Re: [Django] #23301: DateField doesn't work when called 'date'

[Django]

#23301: DateField doesn't work when called 'date'
-+-
 Reporter:  fletom   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by fletom):

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


Old description:

> When called anything else it seems to work fine.
>
> {{{#!python
> m = MyModel(date = datetime.date.today())
> m.save()
> MyModel.objects.get().date # None
>
> # models.py
> class MyModel(models.Model):
> date = models.DateField()
>
> }}}
>
> Running Django 1.6.5. Let me know what else is required to
> debug/reproduce.
>
> Edit: after some testing/process of elimination, it looks like the bug
> isn't quite that simple. Stand by while I figure out exactly how to
> reproduce it.

New description:

 When called anything else it seems to work fine.

 {{{#!python
 m = MyModel(date = datetime.date.today())
 m.save()
 MyModel.objects.get().date # None

 # models.py
 class MyModel(models.Model):
 date = models.DateField()

 }}}

 Running Django 1.6.5. Let me know what else is required to
 debug/reproduce.

 Edit: after some testing/process of elimination, it looks like the bug
 isn't quite that simple. Stand by while I figure out exactly how to
 reproduce it.

 Edit #2: Well, at first I observed this in one of my models, then I
 created a TestModel and obvserved the same thing. Changing the field in
 either model to 'not_called_date' seemed to fix the issue. Now only a few
 minutes later I can't reproduce the bug at all, no matter what I call the
 field. I'll mark this as closed for now, but maybe somebody else will
 encounter something similar in the future.

--

-- 
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.c2c3213b691430f239d2716f99ce4378%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23301: DateField doesn't work when called 'date'

[Django]

#23301: DateField doesn't work when called 'date'
-+-
 Reporter:  fletom   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by fletom):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Old description:

> When called anything else it seems to work fine.
>
> {{{#!python
> m = MyModel(date = datetime.date.today())
> m.save()
> MyModel.objects.get().date # None
>
> # models.py
> class MyModel(models.Model):
> date = models.DateField()
>
> }}}
>
> Running Django 1.6.5. Let me know what else is required to
> debug/reproduce.

New description:

 When called anything else it seems to work fine.

 {{{#!python
 m = MyModel(date = datetime.date.today())
 m.save()
 MyModel.objects.get().date # None

 # models.py
 class MyModel(models.Model):
 date = models.DateField()

 }}}

 Running Django 1.6.5. Let me know what else is required to
 debug/reproduce.

 Edit: after some testing/process of elimination, it looks like the bug
 isn't quite that simple. Stand by while I figure out exactly how 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/064.ebc16993d5872d7372aa6c609efeb50a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23301: DateField doesn't work when called 'date'

[Django]

#23301: DateField doesn't work when called 'date'
--+
 Reporter:  fletom|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.6
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 When called anything else it seems to work fine.

 {{{#!python
 m = MyModel(date = datetime.date.today())
 m.save()
 MyModel.objects.get().date # None

 # models.py
 class MyModel(models.Model):
 date = models.DateField()

 }}}

 Running Django 1.6.5. Let me know what else is required to
 debug/reproduce.

-- 
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/049.0de8e455237258865c9cf356255c6dc4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23295: ALLOWED_HOSTS setting is done in the wrong place, should be in a custom middleware

[Django]

#23295: ALLOWED_HOSTS setting is done in the wrong place, should be in a custom
middleware
---+--
 Reporter:  mark0978   |Owner:  collinanderson
 Type:  Bug|   Status:  closed
Component:  Uncategorized  |  Version:  1.5
 Severity:  Normal |   Resolution:  fixed
 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 Collin Anderson ):

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


Comment:

 In [changeset:"230393e5e81ff524a3ab8c476f75011d3ac53115"]:
 {{{
 #!CommitTicketReference repository=""
 revision="230393e5e81ff524a3ab8c476f75011d3ac53115"
 Fixed #23295 -- Removed unnecessary fix_location_header request.get_host()
 check.
 }}}

-- 
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.859596771ca4e0d2ab90e5330c5308b1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23295: ALLOWED_HOSTS setting is done in the wrong place, should be in a custom middleware

[Django]

#23295: ALLOWED_HOSTS setting is done in the wrong place, should be in a custom
middleware
---+--
 Reporter:  mark0978   |Owner:  collinanderson
 Type:  Bug|   Status:  closed
Component:  Uncategorized  |  Version:  1.5
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Carl Meyer ):

 In [changeset:"9fef66ef7c3dbb156d0b235261ec499f81494eae"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9fef66ef7c3dbb156d0b235261ec499f81494eae"
 Merge pull request #3072 from collinanderson/23295

 Fixed #23295 -- Removed unnecessary fix_location_header request.get_host()
 check
 }}}

-- 
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.2c9b5c39c5008796ae0dfdc176bec972%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 230393: Fixed #23295 -- Removed unnecessary fix_location_h...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 230393e5e81ff524a3ab8c476f75011d3ac53115
  
https://github.com/django/django/commit/230393e5e81ff524a3ab8c476f75011d3ac53115
  Author: Collin Anderson 
  Date:   2014-08-15 (Fri, 15 Aug 2014)

  Changed paths:
M django/http/utils.py
M tests/http_utils/tests.py

  Log Message:
  ---
  Fixed #23295 -- Removed unnecessary fix_location_header request.get_host() 
check.


  Commit: 9fef66ef7c3dbb156d0b235261ec499f81494eae
  
https://github.com/django/django/commit/9fef66ef7c3dbb156d0b235261ec499f81494eae
  Author: Carl Meyer 
  Date:   2014-08-15 (Fri, 15 Aug 2014)

  Changed paths:
M django/http/utils.py
M tests/http_utils/tests.py

  Log Message:
  ---
  Merge pull request #3072 from collinanderson/23295

Fixed #23295 -- Removed unnecessary fix_location_header request.get_host() check


Compare: https://github.com/django/django/compare/90b64db39c4f...9fef66ef7c3d

-- 
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/53ee95de5c9bf_2fe53fe0301c52a076d1%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23300: TestCase.assertTemplateUsed passes erroneously on an HttpResponse (was: TestCase.assertTemplateUsed passes erroniously on an HttpResponse)

[Django]

#23300: TestCase.assertTemplateUsed passes erroneously on an HttpResponse
-+-
 Reporter:  zags |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  asserttemplateused   | Triage Stage:
  template   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by zags):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 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/062.bc722a991fbf8d617fba1fb700f2f0c2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23300: TestCase.assertTemplateUsed passes erroniously on an HttpResponse

[Django]

#23300: TestCase.assertTemplateUsed passes erroniously on an HttpResponse
-+-
 Reporter:  zags |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Testing  |Version:  1.6
  framework  |   Keywords:  asserttemplateused template
 Severity:  Normal   |  Has patch:  1
 Triage Stage:  Unreviewed   |  UI/UX:  0
Easy pickings:  0|
-+-
 The following test should fail.  It is asserting that the response both
 renders and does not render the template "xxx.html", which is a
 contradiction.  However, this test passes.

 {{{
 from django.test import TestCase
 from django.http.response import HttpResponse

 class TestTemplateUsed(TestCase):
 def test_template_used(self):
 response = HttpResponse("xxx")
 self.assertTemplateUsed(response, "xxx.html")
 self.assertTemplateNotUsed(response, "xxx.html")
 }}}

 The issue is that HttpResponse objects have no "template" attribute, which
 assertTemplateUsed interprets as an intention to use a context manager
 rather than an assertion.

 {{{
 def assertTemplateUsed(self, response=None, template_name=None,
 msg_prefix=''):
 #...
 if not hasattr(response, 'templates') or (response is None and
 template_name):
 #...
 }}}

 I'm not sure why this is implemented this way, but from the docs (I can
 only find the 1.5 docs of this feature; I'm not sure where the relevant
 docs are for 1.6 and later), it seems far more sensible to implement this
 as:

 {{{
 def assertTemplateUsed(self, response=None, template_name=None,
 msg_prefix=''):
 #...
 if (response is None and template_name):
 #...
 }}}

 Just to call out an important point, unless I am missing something, this
 feature is entirely undocumented in v1.6 and v1.7

-- 
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/047.3be6722d1df29a2592dce740eb6f76ff%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19716: Support microsecond precision in MySQL ORM DateTimeField

[Django]

#19716: Support microsecond precision in MySQL ORM DateTimeField
-+-
 Reporter:  erik@…   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by claudep):

 We could bump it, but not to 1.2.5. Even Debian unstable has still 1.2.3,
 which might mean that there are other issues with more recent versions.

-- 
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/077.e8959711a838163ddc0fae988bd79eff%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23298: Makemessages --ignore option doesn't work for directories under Windows

[Django]

#23298: Makemessages --ignore option doesn't work for directories under Windows
-+-
 Reporter:  ramiro   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  master
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  makemessages |  Unreviewed
  windows win32 --ignore ignore  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by ramiro):

 Note: To see the test failures, gettext needs to be installed. Otherwise
 these tests are skipped.

-- 
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.c2bf9c59466a9d0b0d7dd9b5fb7c42c2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23298: Makemessages --ignore option doesn't work for directories under Windows

[Django]

#23298: Makemessages --ignore option doesn't work for directories under Windows
-+-
 Reporter:  ramiro   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  master
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  makemessages |  Unreviewed
  windows win32 --ignore ignore  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Description changed by ramiro:

Old description:

> When running the `i18n.test_extraction` tests under Windows, the
> following failures happen:
>
> {{{
> ==
> FAIL: test_ignore_subdirectory
> (i18n.test_extraction.IgnoredExtractorTests)
> --
> Traceback (most recent call last):
>   File "D:\ramiro\django\upstream\tests\i18n\test_extraction.py", line
> 387, in test_ignore_subdirectory
> self.assertTrue("ignoring directory subdir" in out)
> AssertionError: False is not true
>
> ==
> FAIL: test_media_static_dirs_ignored
> (i18n.test_extraction.IgnoredExtractorTests)
> --
> Traceback (most recent call last):
>   File "d:\ramiro\django\upstream\django\test\utils.py", line 281, in
> inner
> return test_func(*args, **kwargs)
>   File "D:\ramiro\django\upstream\tests\i18n\test_extraction.py", line
> 402, in test_media_static_dirs_ignored
> self.assertIn("ignoring directory static_root", out)
> AssertionError: u'ignoring directory static_root' not found in 'examining
> files with the extensions: .html and .txt\nprocessing file __init__.py in
> .\nprocessing file code.sample in .\nprocessing file ignored.html in
> .\\ignore_dir\nprocessing file ja
> vascript.js in .\nprocessing file media_ignored.html in
> .\\media_root\nprocessing file not_utf8.sample in .\nprocessing file
> static_ignored.html in .\\static_root\nprocessing file comments.thtml in
> .\\templates\nprocessing file empty.html in .\\templ
> ates\nprocessing file plural.djtpl in .\\templates\nprocessing file
> ignored.html in .\\templates\\subdir\nprocessing file
> template_with_error.tpl in .\\templates\nprocessing file test.html in
> .\\templates\nprocessing file xxx_ignored.html in .\\templ
> ates\nprocessing locale de\ncopying plural forms: "Plural-Forms:
> nplurals=2; plural=(n != 1);\\n"\n'
>
> --
> Ran 34 tests in 5.670s
>
> FAILED (failures=2)
> }}}
>
> This is caused because code is trying to perform matching of dirs spec
> matching a trailing `/*` but the path representation is uses at that
> point is in native format.
>
> Refs #20422
> Refs #22336

New description:

 When running the `i18n.test_extraction` tests under Windows, the following
 failures happen:

 {{{
 ==
 FAIL: test_ignore_subdirectory
 (i18n.test_extraction.IgnoredExtractorTests)
 --
 Traceback (most recent call last):
   File "D:\ramiro\django\upstream\tests\i18n\test_extraction.py", line
 387, in test_ignore_subdirectory
 self.assertTrue("ignoring directory subdir" in out)
 AssertionError: False is not true

 ==
 FAIL: test_media_static_dirs_ignored
 (i18n.test_extraction.IgnoredExtractorTests)
 --
 Traceback (most recent call last):
   File "d:\ramiro\django\upstream\django\test\utils.py", line 281, in
 inner
 return test_func(*args, **kwargs)
   File "D:\ramiro\django\upstream\tests\i18n\test_extraction.py", line
 402, in test_media_static_dirs_ignored
 self.assertIn("ignoring directory static_root", out)
 AssertionError: u'ignoring directory static_root' not found in 'examining
 files with the extensions: .html and .txt\nprocessing file __init__.py in
 .\nprocessing file code.sample in .\nprocessing file ignored.html in
 .\\ignore_dir\nprocessing file ja
 vascript.js in .\nprocessing file media_ignored.html in
 .\\media_root\nprocessing file not_utf8.sample in .\nprocessing file
 static_ignored.html in .\\static_root\nprocessing file comments.thtml in
 .\\templates\nprocessing file empty.html in .\\templ
 ates\nprocessing file plural.djtpl in .\\templates\nprocessing file
 ignored.html in 

[Django] #23299: Add some interoperability to _() function calls parsing in templatize function.

[Django]

#23299: Add some interoperability to _() function calls parsing in templatize
function.
--+
 Reporter:  niwibe|  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  Internationalization  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+
 The current implementation only works for django and works very well. But
 for make easy use another template engine like jinja2 and combine it with
 django i18n makemessages process, would be awesome include some support
 for more generic parsing of _() function calls.

 The change is very small, it uses findall instead of match, that allows
 finding inner _() function calls that are very common in jinja2 templates
 (and not in django templates):

 https://github.com/niwibe/django/compare/interoprability-jinja-django-
 i18n-parse

-- 
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/049.32a9d0837fbd30d5381ada19a3012b8d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23298: Makemessages --ignore option doesn't work for directories under Windows

[Django]

#23298: Makemessages --ignore option doesn't work for directories under Windows
-+-
 Reporter:  ramiro   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  master
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  makemessages |  Unreviewed
  windows win32 --ignore ignore  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by ramiro):

 * keywords:   => makemessages windows win32 --ignore ignore
 * has_patch:  0 => 1


Comment:

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

-- 
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.04b34bb7aaf92d1fb37d15af3d93e2ed%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] ee7289: [1.7.x] Fixed syntax highlighting and indentation ...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: ee7289656c4aa18df91b3b18fff31cd010109de7
  
https://github.com/django/django/commit/ee7289656c4aa18df91b3b18fff31cd010109de7
  Author: areski 
  Date:   2014-08-15 (Fri, 15 Aug 2014)

  Changed paths:
M docs/topics/logging.txt

  Log Message:
  ---
  [1.7.x] Fixed syntax highlighting and indentation in docs/topics/logging.txt.

Backport of 90b64db39c from master


-- 
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/53ee5cec2a654_577a3fa1ed1812c0115a7%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 90b64d: Fixed syntax highlighting and indentation in docs/...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 90b64db39c4fd1243182068c3a54c3e08cd0f4b9
  
https://github.com/django/django/commit/90b64db39c4fd1243182068c3a54c3e08cd0f4b9
  Author: areski 
  Date:   2014-08-15 (Fri, 15 Aug 2014)

  Changed paths:
M docs/topics/logging.txt

  Log Message:
  ---
  Fixed syntax highlighting and indentation in docs/topics/logging.txt.


-- 
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/53ee5cd3299_5acb3fa9465a72b891556%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[Django] #23298: Makemessages --ignore option doesn't work for directories under Windows

[Django]

#23298: Makemessages --ignore option doesn't work for directories under Windows
+
   Reporter:  ramiro|  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  Internationalization  |Version:  master
   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 |
+
 When running the `i18n.test_extraction` tests under Windows, the following
 failures happen:

 {{{
 ==
 FAIL: test_ignore_subdirectory
 (i18n.test_extraction.IgnoredExtractorTests)
 --
 Traceback (most recent call last):
   File "D:\ramiro\django\upstream\tests\i18n\test_extraction.py", line
 387, in test_ignore_subdirectory
 self.assertTrue("ignoring directory subdir" in out)
 AssertionError: False is not true

 ==
 FAIL: test_media_static_dirs_ignored
 (i18n.test_extraction.IgnoredExtractorTests)
 --
 Traceback (most recent call last):
   File "d:\ramiro\django\upstream\django\test\utils.py", line 281, in
 inner
 return test_func(*args, **kwargs)
   File "D:\ramiro\django\upstream\tests\i18n\test_extraction.py", line
 402, in test_media_static_dirs_ignored
 self.assertIn("ignoring directory static_root", out)
 AssertionError: u'ignoring directory static_root' not found in 'examining
 files with the extensions: .html and .txt\nprocessing file __init__.py in
 .\nprocessing file code.sample in .\nprocessing file ignored.html in
 .\\ignore_dir\nprocessing file ja
 vascript.js in .\nprocessing file media_ignored.html in
 .\\media_root\nprocessing file not_utf8.sample in .\nprocessing file
 static_ignored.html in .\\static_root\nprocessing file comments.thtml in
 .\\templates\nprocessing file empty.html in .\\templ
 ates\nprocessing file plural.djtpl in .\\templates\nprocessing file
 ignored.html in .\\templates\\subdir\nprocessing file
 template_with_error.tpl in .\\templates\nprocessing file test.html in
 .\\templates\nprocessing file xxx_ignored.html in .\\templ
 ates\nprocessing locale de\ncopying plural forms: "Plural-Forms:
 nplurals=2; plural=(n != 1);\\n"\n'

 --
 Ran 34 tests in 5.670s

 FAILED (failures=2)
 }}}

 This is caused because code is trying to perform matching of dirs spec
 matching a trailing `/*` but the path representation is uses at that point
 is in native format.

 Refs #20422
 Refs #22336

-- 
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/049.db71c0e7ea5b62302b325aa1fbaf7697%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20003: URLValidator does not accept urls with usernames or passwords in them

[Django]

#20003: URLValidator does not accept urls with usernames or passwords in them
--+
 Reporter:  marshall@…|Owner:
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:  URLValidator  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * needs_better_patch:  0 => 1


Comment:

 The proposed change appears vulnerable to the "catastrophic backtracking
 situation" described in 9f8287a3f145fe5cbe71ef5573ea8898404727ad as the
 test added there now hangs with the proposed changes. This is one reason
 I'm reluctant to add regex complexity.

-- 
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/079.39c74cf23879fa493ce65e00416b90a1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23296: Invalid parameter to create() in RunPython example

[Django]

#23296: Invalid parameter to create() in RunPython example
-+-
 Reporter:  areski   |Owner:  areski
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.7-rc-2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  migrations   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"28d97533246fa1051e416ff772a40190b1f30e4d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="28d97533246fa1051e416ff772a40190b1f30e4d"
 [1.7.x] Fixed #23296 -- Fixed RunPython code sample in Migration
 Operations.

 Backport of 7ca665c5f5 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/064.847332e014e0356cac39be8d315873f6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 7ca665: Fixed #23296 -- Fixed RunPython code sample in Mig...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 7ca665c5f593953cba2cfeebd4f82acd38231031
  
https://github.com/django/django/commit/7ca665c5f593953cba2cfeebd4f82acd38231031
  Author: areski 
  Date:   2014-08-15 (Fri, 15 Aug 2014)

  Changed paths:
M docs/ref/migration-operations.txt

  Log Message:
  ---
  Fixed #23296 -- Fixed RunPython code sample in Migration Operations.


-- 
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/53ee49f9bca9e_6223fadc4b012b833988%40hookshot-fe3-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 28d975: [1.7.x] Fixed #23296 -- Fixed RunPython code sampl...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 28d97533246fa1051e416ff772a40190b1f30e4d
  
https://github.com/django/django/commit/28d97533246fa1051e416ff772a40190b1f30e4d
  Author: areski 
  Date:   2014-08-15 (Fri, 15 Aug 2014)

  Changed paths:
M docs/ref/migration-operations.txt

  Log Message:
  ---
  [1.7.x] Fixed #23296 -- Fixed RunPython code sample in Migration Operations.

Backport of 7ca665c5f5 from master


-- 
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/53ee4a29690b0_eb73ff03eaa52bc219a0%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23296: Invalid parameter to create() in RunPython example

[Django]

#23296: Invalid parameter to create() in RunPython example
-+-
 Reporter:  areski   |Owner:  areski
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.7-rc-2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  migrations   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"7ca665c5f593953cba2cfeebd4f82acd38231031"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7ca665c5f593953cba2cfeebd4f82acd38231031"
 Fixed #23296 -- Fixed RunPython code sample in Migration Operations.
 }}}

-- 
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.d9d098fb075ea1ea3e3e1997c1985895%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23295: ALLOWED_HOSTS setting is done in the wrong place, should be in a custom middleware

[Django]

#23295: ALLOWED_HOSTS setting is done in the wrong place, should be in a custom
middleware
---+--
 Reporter:  mark0978   |Owner:  collinanderson
 Type:  Bug|   Status:  assigned
Component:  Uncategorized  |  Version:  1.5
 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 collinanderson):

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


Comment:

 I've attached a (super simple) test. Buildbot pending
 http://djangoci.com/job/django-pull-requests/735/

-- 
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.dcf61f9501d57c0a7e192a3ec3ed6dca%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23288: Unable to correctly access data in table during migration

[Django]

#23288: Unable to correctly access data in table during migration
-+-
 Reporter:  mtthw-meyer  |Owner:
 Type:  Bug  |  andrewgodwin
Component:  Migrations   |   Status:  closed
 Severity:  Release blocker  |  Version:  1.7-rc-2
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"41cf159c0ac0a7380874cb6f17464dd741ad1d9b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="41cf159c0ac0a7380874cb6f17464dd741ad1d9b"
 [1.7.x] Fixed #23294 -- Add related_name to existing migrations.

 Thanks to Florian Apolloner for the review; refs #23288.

 Backport of 1d79d08d9a 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/069.cca971824b06036aaf17e2db4a061849%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23294: add related_name to existing migrations

[Django]

#23294: add related_name to existing migrations
-+-
 Reporter:  collinanderson   |Owner:
 Type:  Bug  |  collinanderson
Component:  Migrations   |   Status:  closed
 Severity:  Release blocker  |  Version:  1.7-rc-2
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"41cf159c0ac0a7380874cb6f17464dd741ad1d9b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="41cf159c0ac0a7380874cb6f17464dd741ad1d9b"
 [1.7.x] Fixed #23294 -- Add related_name to existing migrations.

 Thanks to Florian Apolloner for the review; refs #23288.

 Backport of 1d79d08d9a 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/072.7240dd88e5e714bad6003e53aef83cb2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 41cf15: [1.7.x] Fixed #23294 -- Add related_name to existi...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 41cf159c0ac0a7380874cb6f17464dd741ad1d9b
  
https://github.com/django/django/commit/41cf159c0ac0a7380874cb6f17464dd741ad1d9b
  Author: Collin Anderson 
  Date:   2014-08-15 (Fri, 15 Aug 2014)

  Changed paths:
M django/contrib/auth/migrations/0001_initial.py

  Log Message:
  ---
  [1.7.x] Fixed #23294 -- Add related_name to existing migrations.

Thanks to Florian Apolloner for the review; refs #23288.

Backport of 1d79d08d9a from master


-- 
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/53ee48d63ced_65a93fe115fb32a01025af%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23296: Invalid parameter to create() in RunPython example

[Django]

#23296: Invalid parameter to create() in RunPython example
-+-
 Reporter:  areski   |Owner:  areski
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  1.7-rc-2
 Severity:  Normal   |   Resolution:
 Keywords:  migrations   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by collinanderson):

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


Comment:

 lgtm

-- 
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.bf0b2aa9dbc6f12c3b4532697c79b8a1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23297: Integrity errors in Django admin with custom User model

[Django]

#23297: Integrity errors in Django admin with custom User model
-+--
 Reporter:  dustinfarris |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  contrib.auth |  Version:  1.7-rc-2
 Severity:  Release blocker  |   Resolution:  worksforme
 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 dustinfarris):

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


-- 
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/070.8147d6d7c409c6ad2792f801430c9b17%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23297: Integrity errors in Django admin with custom User model

[Django]

#23297: Integrity errors in Django admin with custom User model
-+--
 Reporter:  dustinfarris |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  contrib.auth |  Version:  1.7-rc-2
 Severity:  Release blocker  |   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 dustinfarris):

 Ack, classic case of me changing AUTH_USER_MODEL later in the project.

 If anyone else runs into this, you need to re-create your django_admin_log
 table because it has a foreign key to the original user model:

 {{{
 ./manage.py dbshell

 DROP TABLE django_admin_log;
 }}}

 and then:

 {{{
 ./manage.py sqlmigrate admin 0001 | ./manage.py dbshell
 }}}

-- 
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/070.6bccc358e039000684230926669c3e14%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23296: Invalid parameter to create() in RunPython example

[Django]

#23296: Invalid parameter to create() in RunPython example
---+
 Reporter:  areski |Owner:  areski
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  Version:  1.7-rc-2
 Severity:  Normal |   Resolution:
 Keywords:  migrations | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by areski):

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


Comment:

 +1 for best practices!

 Here a [https://github.com/django/django/pull/3073 PR] if we are happy
 with this change

-- 
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.291b0664c0f9274492861aa32859c4af%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23297: Integrity errors in Django admin with custom User model (was: Integrity error saving Site with custom User model)

[Django]

#23297: Integrity errors in Django admin with custom User model
-+--
 Reporter:  dustinfarris |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  contrib.auth |  Version:  1.7-rc-2
 Severity:  Release blocker  |   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 dustinfarris):

 * needs_better_patch:   => 0
 * component:  contrib.sites => contrib.auth
 * needs_tests:   => 0
 * needs_docs:   => 0


Old description:

> I use a custom User model: accounts.User
>
> When trying to update an entry for a django.Site record in the Django
> admin:
>
> {{{
> IntegrityError: insert or update on table "django_admin_log" violates
> foreign key constraint
> "django_admin_log_user_id_41e5d33e37dd3226_fk_auth_user_id"
> DETAIL:  Key (user_id)=(4) is not present in table "auth_user".
> }}}
>
> {{{
> Stacktrace (most recent call last):
>
>   File "django/core/handlers/base.py", line 111, in get_response
> response = wrapped_callback(request, *callback_args,
> **callback_kwargs)
>   File "django/contrib/admin/options.py", line 546, in wrapper
> return self.admin_site.admin_view(view)(*args, **kwargs)
>   File "django/utils/decorators.py", line 105, in _wrapped_view
> response = view_func(request, *args, **kwargs)
>   File "django/views/decorators/cache.py", line 52, in _wrapped_view_func
> response = view_func(request, *args, **kwargs)
>   File "django/contrib/admin/sites.py", line 204, in inner
> return view(request, *args, **kwargs)
>   File "django/contrib/admin/options.py", line 1416, in change_view
> return self.changeform_view(request, object_id, form_url,
> extra_context)
>   File "django/utils/decorators.py", line 29, in _wrapper
> return bound_func(*args, **kwargs)
>   File "django/utils/decorators.py", line 105, in _wrapped_view
> response = view_func(request, *args, **kwargs)
>   File "django/utils/decorators.py", line 25, in bound_func
> return func.__get__(self, type(self))(*args2, **kwargs2)
>   File "django/db/transaction.py", line 394, in inner
> return func(*args, **kwargs)
>   File "django/db/transaction.py", line 339, in __exit__
> connection.commit()
>   File "django/db/backends/__init__.py", line 176, in commit
> self._commit()
>   File "django/db/backends/__init__.py", line 145, in _commit
> return self.connection.commit()
>   File "django/db/utils.py", line 94, in __exit__
> six.reraise(dj_exc_type, dj_exc_value, traceback)
>   File "django/utils/six.py", line 549, in reraise
> raise value.with_traceback(tb)
>   File "django/db/backends/__init__.py", line 145, in _commit
> return self.connection.commit()
> }}}

New description:

 I use a custom User model: accounts.User

 When trying to save anything in the Django admin, I get:

 {{{
 IntegrityError: insert or update on table "django_admin_log" violates
 foreign key constraint
 "django_admin_log_user_id_41e5d33e37dd3226_fk_auth_user_id"
 DETAIL:  Key (user_id)=(4) is not present in table "auth_user".
 }}}

 {{{
 Stacktrace (most recent call last):

   File "django/core/handlers/base.py", line 111, in get_response
 response = wrapped_callback(request, *callback_args,
 **callback_kwargs)
   File "django/contrib/admin/options.py", line 546, in wrapper
 return self.admin_site.admin_view(view)(*args, **kwargs)
   File "django/utils/decorators.py", line 105, in _wrapped_view
 response = view_func(request, *args, **kwargs)
   File "django/views/decorators/cache.py", line 52, in _wrapped_view_func
 response = view_func(request, *args, **kwargs)
   File "django/contrib/admin/sites.py", line 204, in inner
 return view(request, *args, **kwargs)
   File "django/contrib/admin/options.py", line 1416, in change_view
 return self.changeform_view(request, object_id, form_url,
 extra_context)
   File "django/utils/decorators.py", line 29, in _wrapper
 return bound_func(*args, **kwargs)
   File "django/utils/decorators.py", line 105, in _wrapped_view
 response = view_func(request, *args, **kwargs)
   File "django/utils/decorators.py", line 25, in bound_func
 return func.__get__(self, type(self))(*args2, **kwargs2)
   File "django/db/transaction.py", line 394, in inner
 return func(*args, **kwargs)
   File "django/db/transaction.py", line 339, in __exit__
 connection.commit()
   File "django/db/backends/__init__.py", line 176, in commit
 self._commit()
   File "django/db/backends/__init__.py", line 145, in _commit
 return self.connection.commit()
   File "django/db/utils.py", 

[Django] #23297: Integrity error saving Site with custom User model

[Django]

#23297: Integrity error saving Site with custom User model
-+--
 Reporter:  dustinfarris |  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  contrib.sites|Version:  1.7-rc-2
 Severity:  Release blocker  |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+--
 I use a custom User model: accounts.User

 When trying to update an entry for a django.Site record in the Django
 admin:

 {{{
 IntegrityError: insert or update on table "django_admin_log" violates
 foreign key constraint
 "django_admin_log_user_id_41e5d33e37dd3226_fk_auth_user_id"
 DETAIL:  Key (user_id)=(4) is not present in table "auth_user".
 }}}

 {{{
 Stacktrace (most recent call last):

   File "django/core/handlers/base.py", line 111, in get_response
 response = wrapped_callback(request, *callback_args,
 **callback_kwargs)
   File "django/contrib/admin/options.py", line 546, in wrapper
 return self.admin_site.admin_view(view)(*args, **kwargs)
   File "django/utils/decorators.py", line 105, in _wrapped_view
 response = view_func(request, *args, **kwargs)
   File "django/views/decorators/cache.py", line 52, in _wrapped_view_func
 response = view_func(request, *args, **kwargs)
   File "django/contrib/admin/sites.py", line 204, in inner
 return view(request, *args, **kwargs)
   File "django/contrib/admin/options.py", line 1416, in change_view
 return self.changeform_view(request, object_id, form_url,
 extra_context)
   File "django/utils/decorators.py", line 29, in _wrapper
 return bound_func(*args, **kwargs)
   File "django/utils/decorators.py", line 105, in _wrapped_view
 response = view_func(request, *args, **kwargs)
   File "django/utils/decorators.py", line 25, in bound_func
 return func.__get__(self, type(self))(*args2, **kwargs2)
   File "django/db/transaction.py", line 394, in inner
 return func(*args, **kwargs)
   File "django/db/transaction.py", line 339, in __exit__
 connection.commit()
   File "django/db/backends/__init__.py", line 176, in commit
 self._commit()
   File "django/db/backends/__init__.py", line 145, in _commit
 return self.connection.commit()
   File "django/db/utils.py", line 94, in __exit__
 six.reraise(dj_exc_type, dj_exc_value, traceback)
   File "django/utils/six.py", line 549, in reraise
 raise value.with_traceback(tb)
   File "django/db/backends/__init__.py", line 145, in _commit
 return self.connection.commit()
 }}}

-- 
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/055.ebdca920375a5dfdb83fc4070d135b54%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19716: Support microsecond precision in MySQL ORM DateTimeField

[Django]

#19716: Support microsecond precision in MySQL ORM DateTimeField
-+-
 Reporter:  erik@…   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by timgraham):

 Would it be unreasonable to bump the minimum version of MySQLdb we
 support? It seems we currently require 1.2.1 or later
 (django.db.backends.mysql.base). I assume the only reason to use an older
 version is if you want to use the global packages provided by your OS
 instead of virtualenv, etc.

-- 
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/077.6e562d95ca2f54c4c2103d916854feff%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23295: ALLOWED_HOSTS setting is done in the wrong place, should be in a custom middleware

[Django]

#23295: ALLOWED_HOSTS setting is done in the wrong place, should be in a custom
middleware
---+--
 Reporter:  mark0978   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  1.5
 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 carljm):

 Replying to [comment:3 collinanderson]:
 > Well, it doesn't break any tests to remove the " and request.get_host()"
 check.
 > https://github.com/django/django/pull/3072

 Nice, seems fine to me. I think if we do that we should also add a test
 verifying that `get_host` is never called by `fix_location_header` if the
 location header is already a full URL; otherwise the motivating use case
 here could regress without it being caught.

-- 
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.ea7912bcad144dee049b304f2aa36c06%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23295: ALLOWED_HOSTS setting is done in the wrong place, should be in a custom middleware

[Django]

#23295: ALLOWED_HOSTS setting is done in the wrong place, should be in a custom
middleware
---+--
 Reporter:  mark0978   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  1.5
 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 collinanderson):

 Well, it doesn't break any tests to remove the " and request.get_host()"
 check.
 https://github.com/django/django/pull/3072

-- 
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.28a6b1a0848d7154b776fd579dfce593%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23294: add related_name to existing migrations

[Django]

#23294: add related_name to existing migrations
-+-
 Reporter:  collinanderson   |Owner:
 Type:  Bug  |  collinanderson
Component:  Migrations   |   Status:  closed
 Severity:  Release blocker  |  Version:  1.7-rc-2
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"1d79d08d9aef1565cf56d50f0742285efae53631"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1d79d08d9aef1565cf56d50f0742285efae53631"
 Fixed #23294 -- Add related_name to existing migrations.

 Thanks to Florian Apolloner for the review; refs #23288.
 }}}

-- 
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.14d147006940031696bfbe7071e2afad%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23288: Unable to correctly access data in table during migration

[Django]

#23288: Unable to correctly access data in table during migration
-+-
 Reporter:  mtthw-meyer  |Owner:
 Type:  Bug  |  andrewgodwin
Component:  Migrations   |   Status:  closed
 Severity:  Release blocker  |  Version:  1.7-rc-2
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"1d79d08d9aef1565cf56d50f0742285efae53631"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1d79d08d9aef1565cf56d50f0742285efae53631"
 Fixed #23294 -- Add related_name to existing migrations.

 Thanks to Florian Apolloner for the review; refs #23288.
 }}}

-- 
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.739dc5b9337fc26ce577ef402bec8fb5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 1d79d0: Fixed #23294 -- Add related_name to existing migra...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1d79d08d9aef1565cf56d50f0742285efae53631
  
https://github.com/django/django/commit/1d79d08d9aef1565cf56d50f0742285efae53631
  Author: Collin Anderson 
  Date:   2014-08-15 (Fri, 15 Aug 2014)

  Changed paths:
M django/contrib/auth/migrations/0001_initial.py

  Log Message:
  ---
  Fixed #23294 -- Add related_name to existing migrations.

Thanks to Florian Apolloner for the review; refs #23288.


-- 
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/53ee37c738713_66d23ff8313192a01079d8%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23278: django.db.backends.schema logger isn't documented

[Django]

#23278: django.db.backends.schema logger isn't documented
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.7-rc-2
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"3af14109499bba8ea5b2a94e6a26cecb6cc002cd"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3af14109499bba8ea5b2a94e6a26cecb6cc002cd"
 [1.7.x] Fixed #23278 -- Documented django.db.backends.schema logger

 Backport of ef90d395ab 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/067.8801e7003662eaa4b0b9ef22c04e9d0d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 3af141: [1.7.x] Fixed #23278 -- Documented django.db.backe...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 3af14109499bba8ea5b2a94e6a26cecb6cc002cd
  
https://github.com/django/django/commit/3af14109499bba8ea5b2a94e6a26cecb6cc002cd
  Author: areski 
  Date:   2014-08-15 (Fri, 15 Aug 2014)

  Changed paths:
M docs/topics/logging.txt

  Log Message:
  ---
  [1.7.x] Fixed #23278 -- Documented django.db.backends.schema logger

Backport of ef90d395ab from master


-- 
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/53ee3776e1752_4ef3f7fe547d2a0954bc%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20003: URLValidator does not accept urls with usernames or passwords in them

[Django]

#20003: URLValidator does not accept urls with usernames or passwords in them
--+
 Reporter:  marshall@…|Owner:
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:  URLValidator  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by dbrgn):

 @collinanderson I don't think so. The job of the URLValidator is to test
 whether an URL is valid according to some RFCs, not to decide whether a
 specific URL is a good idea in a specific case :)

 It could have been a security issue if `verify_exists` were still
 available (e.g. because the credentials would show up in network traffic),
 but as this functionality has been removed in 1.5 that's not a concern
 anymore.

-- 
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/079.13ccd99fde10593a090e61fdac78da19%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] ef90d3: Fixed #23278 -- Documented django.db.backends.sche...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ef90d395abfc4a9b0338146cf456f68d4f0557c7
  
https://github.com/django/django/commit/ef90d395abfc4a9b0338146cf456f68d4f0557c7
  Author: areski 
  Date:   2014-08-15 (Fri, 15 Aug 2014)

  Changed paths:
M docs/topics/logging.txt

  Log Message:
  ---
  Fixed #23278 -- Documented django.db.backends.schema logger


-- 
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/53ee36b81c405_5f3e3faa3fc3d2b878199%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23295: ALLOWED_HOSTS setting is done in the wrong place, should be in a custom middleware

[Django]

#23295: ALLOWED_HOSTS setting is done in the wrong place, should be in a custom
middleware
---+--
 Reporter:  mark0978   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  1.5
 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 carljm):

 The reason for performing the check in `get_host` is that there was no
 other way to catch all the instances of people using the request host in
 their own code. Leaving `get_host` alone and doing the check in
 `CommonMiddleware` would have fixed only a small portion of
 vulnerabilities related to spoofed hosts, leaving all others wide open.
 Returning a possibly-spoofed value from `get_host` would be a security
 vulnerability.

 The behavior you want is a bit specialized, so I don't think it's
 problematic that it requires a bit of custom code to implement. I don't
 entirely understand the code you posted. For instance, why do you need the
 `process_response` check? AFAICT `CommonMiddleware.process_response` does
 not call `get_host` (unless you have `SEND_BROKEN_LINK_EMAILS=True` (now
 deprecated) and the response is a 404).

 You have a valid point about the `fix_location_header` response-fix
 function that is run unconditionally, and always checks
 `request.get_host()` for redirect responses. I'm not sure why
 `fix_location_header` needs to check `get_host` in advance, rather than
 just calling `build_absolute_uri`. If it did the latter, then if you
 already had a full URL in your `Location` header, `build_absolute_uri`
 would bail early and never call `get_host` at all, which would take care
 of your case.

-- 
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.a15e4473efd9c79abab9bde2bcdaaaf7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23296: Invalid parameter to create() in RunPython example (was: RunPython)

[Django]

#23296: Invalid parameter to create() in RunPython example
---+
 Reporter:  areski |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.7-rc-2
 Severity:  Normal |   Resolution:
 Keywords:  migrations | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by timgraham):

 If we are showing best practices, how about using
 `.using(db_alias).bulk_create(...)`?

-- 
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.34c4a88711794dfd9087951438155572%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21450: BaseYearArchiveView prevent ordering of queryset

[Django]

#21450: BaseYearArchiveView prevent ordering of queryset
-+-
 Reporter:  Thibault Serot   |Owner:  nobody
    |   Status:  closed
 Type:   |  Version:  1.5
  Cleanup/optimization   |   Resolution:  fixed
Component:  Generic views| Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  BaseYearArchiveView  |  Patch needs improvement:  0
  filtering  |UI/UX:  0
Has patch:  0|
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timgraham):

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


Comment:

 Closing per above commit as I believe it solves it, but please reopen if
 not.

-- 
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/094.a063b03b273d7010ba64dd778aba2bea%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 2724cd: Fixed #18355 -- Added ordering options to list bas...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2724cdbff635a40819f206411de23e9b14867a58
  
https://github.com/django/django/commit/2724cdbff635a40819f206411de23e9b14867a58
  Author: Peter Harley 
  Date:   2014-08-15 (Fri, 15 Aug 2014)

  Changed paths:
M django/views/generic/dates.py
M django/views/generic/list.py
M docs/ref/class-based-views/flattened-index.txt
M docs/ref/class-based-views/mixins-multiple-object.txt
M docs/releases/1.8.txt
M tests/generic_views/test_dates.py
M tests/generic_views/test_list.py
M tests/generic_views/urls.py
M tests/generic_views/views.py

  Log Message:
  ---
  Fixed #18355 -- Added ordering options to list based generic views.

Added MultipleObjectMixin.ordering and get_ordering().

Refs #21450.


-- 
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/53ee22d072f61_67993fbae0d8329c98553%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23296: RunPython

[Django]

#23296: RunPython
---+
 Reporter:  areski |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.7-rc-2
 Severity:  Normal |   Resolution:
 Keywords:  migrations | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by collinanderson):

 * cc: cmawebsite@… (added)
 * needs_better_patch:   => 0
 * component:  Migrations => Documentation
 * needs_tests:   => 0
 * version:  master => 1.7-rc-2
 * needs_docs:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 I think that's a problem with the docs. I don't think `create()` accepts
 `using`.

 Maybe should we say?
 `Country(name="USA", code="us").save(using=db_alias)`

 This syntax may also work:
 `Country.objects.using(db_alias).create(name="USA", code="us")`

-- 
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.5af18f9d306b467b2f4fc6498d3a7654%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18355: Add ordering mixin for class based generic views

[Django]

#18355: Add ordering mixin for class based generic views
---+-
 Reporter:  aaugustin  |Owner:  pjrharley
 Type:  New feature|   Status:  closed
Component:  Generic views  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"2724cdbff635a40819f206411de23e9b14867a58"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2724cdbff635a40819f206411de23e9b14867a58"
 Fixed #18355 -- Added ordering options to list based generic views.

 Added MultipleObjectMixin.ordering and get_ordering().

 Refs #21450.
 }}}

-- 
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.ada379f21ce8bb64388ba139ab771a95%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21450: BaseYearArchiveView prevent ordering of queryset

[Django]

#21450: BaseYearArchiveView prevent ordering of queryset
-+-
 Reporter:  Thibault Serot   |Owner:  nobody
    |   Status:  new
 Type:   |  Version:  1.5
  Cleanup/optimization   |   Resolution:
Component:  Generic views| Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  BaseYearArchiveView  |  Patch needs improvement:  0
  filtering  |UI/UX:  0
Has patch:  0|
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"2724cdbff635a40819f206411de23e9b14867a58"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2724cdbff635a40819f206411de23e9b14867a58"
 Fixed #18355 -- Added ordering options to list based generic views.

 Added MultipleObjectMixin.ordering and get_ordering().

 Refs #21450.
 }}}

-- 
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/094.b8898162bd4b762795cf433e9b8b38c7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 6011f2: [1.7.x] Fixed typo in tests/migrations/test_operat...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 6011f245036ad1a652881e65b4b25cc5773bfb1b
  
https://github.com/django/django/commit/6011f245036ad1a652881e65b4b25cc5773bfb1b
  Author: Tim Graham 
  Date:   2014-08-15 (Fri, 15 Aug 2014)

  Changed paths:
M tests/migrations/test_operations.py

  Log Message:
  ---
  [1.7.x] Fixed typo in tests/migrations/test_operations.py

Backport of 0ad4672c0f from master


-- 
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/53ee22ce5dfff_10803ff294ac729c10055%40hookshot-fe3-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 0ad467: Fixed typo in tests/migrations/test_operations.py

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 0ad4672c0f9cc8fb819abbc97c13ceaffc011a7d
  
https://github.com/django/django/commit/0ad4672c0f9cc8fb819abbc97c13ceaffc011a7d
  Author: Tim Graham 
  Date:   2014-08-15 (Fri, 15 Aug 2014)

  Changed paths:
M tests/migrations/test_operations.py

  Log Message:
  ---
  Fixed typo in tests/migrations/test_operations.py


-- 
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/53ee20ef434c1_11673fb0b9bbd2b81051c5%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[Django] #23296: RunPython

[Django]

#23296: RunPython
+
 Reporter:  areski  |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  master
 Severity:  Normal  |   Keywords:  migrations
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 Following RunPython documentation:
 https://docs.djangoproject.com/en/dev/ref/migration-operations/#runpython

 I noticed that I could not get the example running if I use argument
 '''using=db_alias'''.

 It raises the following error:
 {{{
   File "../../django/django/db/models/base.py", line 457, in
 Model.__init__
 self = 
 *args = ()
 **kwargs = {'using': 'default'}
 455 pass
 456 if kwargs:
 --> 457 raise TypeError("'%s' is an invalid keyword argument for
 this function" % list(kwargs)[0])
 args_len = 0
 field = 
 fields_iter = 
 is_related_object = False
 prop = 'using'
 val = u'name1'
 458 super(Model, self).__init__()
 459 signals.post_init.send(sender=self.__class__, instance=self)
 TypeError: 'using' is an invalid keyword argument for this function

 }}}


 Nevertheless if I remove '''using=db_alias''' it works fine, replacing:
 {{{
 db_alias = schema_editor.connection.alias
 Country.objects.create(name="USA", code="us", using=db_alias)
 Country.objects.create(name="France", code="fr", using=db_alias)
 }}}
 by:
 {{{
 Country.objects.create(name="USA", code="us")
 Country.objects.create(name="France", code="fr")
 }}}

 Is this a bug or an error in the documentation?

-- 
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/049.b9315fa8ca141826620bf6a557a95365%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19716: Support microsecond precision in MySQL ORM DateTimeField

[Django]

#19716: Support microsecond precision in MySQL ORM DateTimeField
-+-
 Reporter:  erik@…   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by claudep):

 Reference to MySQLdb bug: https://github.com/farcepest/MySQLdb1/issues/24

-- 
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/077.0fb118ec1f368557969acc9f8fc8b947%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19716: Support microsecond precision in MySQL ORM DateTimeField

[Django]

#19716: Support microsecond precision in MySQL ORM DateTimeField
-+-
 Reporter:  erik@…   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

 * needs_better_patch:  0 => 1


Comment:

 I have a good news and a bad news:
 - the good news is that I found and fixed the source of the test failures
 mentioned above (in `adapt_datetime_with_timezone_support`).
 - the bad news is that we need a very recent version of MySQLdb (1.2.5
 released on January 2 2014) to have a bug fixed when retrieving datetime
 value with microseconds from the database, unless we obtain `None`. The
 patch will need to check and document that limitation.

-- 
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/077.10d0ca0b90c9a71789d80ad9c65a1845%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23295: ALLOWED_HOSTS setting is done in the wrong place, should be in a custom middleware

[Django]

#23295: ALLOWED_HOSTS setting is done in the wrong place, should be in a custom
middleware
---+--
 Reporter:  mark0978   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  1.5
 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 collinanderson):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Interesting. Could hooking into Django's logging solve your problem?
 https://docs.djangoproject.com/en/1.6/topics/logging/#django-security

-- 
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.3190ab7a3936508a1c9c919831502525%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23294: add related_name to existing migrations

[Django]

#23294: add related_name to existing migrations
-+-
 Reporter:  collinanderson   |Owner:
 Type:  Bug  |  collinanderson
Component:  Migrations   |   Status:  new
 Severity:  Release blocker  |  Version:  1.7-rc-2
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Unreviewed => 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/072.70f83cc42973d6e1b810dfe6ff33b011%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23295: ALLOWED_HOSTS setting is done in the wrong place, should be in a custom middleware

[Django]

#23295: ALLOWED_HOSTS setting is done in the wrong place, should be in a custom
middleware
---+
 Reporter:  mark0978   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Right now ALLOWED_HOST checking is done in Request.get_host() which is
 called by CommonMiddleware. And then called again in
 fix_location_header(request, response) which means it is impossible to
 redirect an attacker to fbi.gov and at the same time record their attack
 because on a redirect get_host is called twice!

 Raising a suspicious operation just does not belong in Request.get_host(),
 it really isn't part of the function that gives you the host back, it is
 something you do after you get the host information.

 This is what I've had to write to work around this problem:

 {{{#!python
 class CommonMiddleware(DjangoCommonMiddleware):
 """ In an effort to stop the deluge of ALLOWED_HOSTS emails sent at
 our software
 by very stupid pentesters, I have decided to record what they are
 doing, and then
 send them to the fbi.gov site (out of spite).  It shall be interesting
 to see
 if they actually figure it out or not. (But right now I can't do that
 because of
 limitations within Django"""

 def process_request(self, request):

 def get_client_ip(request):
 x_forwarded_for = request.META.get('HTTP_X_FORWARDED_FOR')
 if x_forwarded_for:
 ip = x_forwarded_for.split(',')[0]
 else:
 ip = request.META.get('REMOTE_ADDR')
 return ip

 try:
 return super(CommonMiddleware, self).process_request(request)
 except SuspiciousOperation as xcpt:
 if 'ALLOWED_HOSTS' in str(xcpt):
 # We try three options, in order of decreasing preference.
 if settings.USE_X_FORWARDED_HOST and (
 'HTTP_X_FORWARDED_HOST' in request.META):
 host = request.META['HTTP_X_FORWARDED_HOST']
 elif 'HTTP_HOST' in request.META:
 host = request.META['HTTP_HOST']
 else:
 # Reconstruct the host using the algorithm from PEP
 333.
 host = request.META['SERVER_NAME']
 server_port = str(request.META['SERVER_PORT'])
 if server_port != ('443' if request.is_secure() else
 '80'):
 host = '%s:%s' % (host, server_port)

 obj = AllowedHostViolation.objects.create(
 host_attacked=host,
 url_attacked=request.get_full_path(),
 attacker=get_client_ip(request)
 )
 response = HttpResponse("You were hoping to have breached
 security!"
 " Not today though!"
 " Now smile for the camera,
 because you've been busted!\n",
 content_type='application/text',
 status=418)
 response.allowed_host_violation = True
 return response
 raise

 def process_response(self, request, response):
 """ Have to also do this to keep it from throwing another
 Suspicious Operation """
 if response.allowed_host_violation:
 return response

 return super(CommonMiddleware, self).process_response(request,
 response)

 }}}

 This bug is also present in 1.6 but in that case you get a differentiated
 Exception thrown.  You still can't return a HttpResponseRedirect to send
 them all to fbi.gov though because the logic is in the wrong place.

-- 
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.157cc83ec30a83a1ce4d469a2e07a718%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23294: add related_name to existing migrations

[Django]

#23294: add related_name to existing migrations
-+-
 Reporter:  collinanderson   |Owner:
 Type:  Bug  |  collinanderson
Component:  Migrations   |   Status:  new
 Severity:  Release blocker  |  Version:  1.7-rc-2
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:
  Needs tests:  0|  Unreviewed
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by collinanderson):

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


Comment:

 https://github.com/django/django/pull/3070

-- 
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.69ab5af119d255ea168b985e25af6c56%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23294: add related_name to existing migrations

[Django]

#23294: add related_name to existing migrations
-+
 Reporter:  collinanderson   |  Owner:  collinanderson
 Type:  Bug  | Status:  new
Component:  Migrations   |Version:  1.7-rc-2
 Severity:  Release blocker  |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 need to add related_name to existing migrations after #23288

-- 
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.3ba38cd52587d17e4e483b477b9bc12c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23287: Change exception message for django.utils.decorators.classonlymethod

[Django]

#23287: Change exception message for django.utils.decorators.classonlymethod
-+-
 Reporter:  zsoldosp |Owner:  timgraham
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Utilities|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"64bb122c3dede3538294bab07d5f1a1980713d31"]:
 {{{
 #!CommitTicketReference repository=""
 revision="64bb122c3dede3538294bab07d5f1a1980713d31"
 Fixed #23287 -- Updated error message for classonlymethod decorator.
 }}}

-- 
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.645660869cc6a3eb52f8b70907335cae%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 64bb12: Fixed #23287 -- Updated error message for classonl...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 64bb122c3dede3538294bab07d5f1a1980713d31
  
https://github.com/django/django/commit/64bb122c3dede3538294bab07d5f1a1980713d31
  Author: Tim Graham 
  Date:   2014-08-15 (Fri, 15 Aug 2014)

  Changed paths:
M django/utils/decorators.py

  Log Message:
  ---
  Fixed #23287 -- Updated error message for classonlymethod decorator.


-- 
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/53ee099f8b68a_ae63fc73221729c56590%40hookshot-fe3-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23287: Change exception message for django.utils.decorators.classonlymethod

[Django]

#23287: Change exception message for django.utils.decorators.classonlymethod
-+-
 Reporter:  zsoldosp |Owner:  timgraham
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:
Component:  Utilities|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timgraham):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * component:  Uncategorized => Utilities
 * needs_tests:   => 0
 * owner:  nobody => timgraham
 * needs_docs:   => 0
 * 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.eff01693d076b6ee64daec616b997f34%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22280: "Conflicting models in application" RuntimeError for same model with different paths

[Django]

#22280: "Conflicting models in application" RuntimeError for same model with
different paths
---+
 Reporter:  blueyed|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  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
---+
Changes (by collinanderson):

 * cc: cmawebsite@… (added)


Comment:

 You either need to move your `apps` folder next `manage.py` or reference
 things as `Baillee.apps.usconst` instead of `apps.usconst`. Always
 reference absolute import paths relative to manage.py

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To 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.3d221bd6cfe60817c1a557a389be63d5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19716: Support microsecond precision in MySQL ORM DateTimeField

[Django]

#19716: Support microsecond precision in MySQL ORM DateTimeField
-+-
 Reporter:  erik@…   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

 * needs_tests:  1 => 0


Comment:

 The current state of the patch seems to generate two failures in the test
 suite (https://github.com/django/django/pull/3049#issuecomment-52261704).

-- 
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/077.0c73a1515019f3af16726763f19ba9e8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23269: Deprecate django.utils.remove_tags() and removetags template filter

[Django]

#23269: Deprecate django.utils.remove_tags() and removetags template filter
-+-
 Reporter:  timgraham|Owner:  timgraham
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Template system  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"e122facbd89c5768528f5ba3b13552d43f989757"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e122facbd89c5768528f5ba3b13552d43f989757"
 Fixed #23269 -- Deprecated django.utils.remove_tags() and removetags
 filter.

 Also the unused, undocumented django.utils.html.strip_entities() function.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To 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.04d8e3a0b941b635a0e38f49e51a61c5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23278: django.db.backends.schema logger isn't documented

[Django]

#23278: django.db.backends.schema logger isn't documented
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.7-rc-2
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by areski):

 * cc: areski (added)
 * has_patch:  0 => 1


Comment:

 Here a [https://github.com/django/django/pull/3069 PR] to add the
 ''django.db.backends.schema'' logger documentation

-- 
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.4e3e7249640569ecbce6192adf7a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] e122fa: Fixed #23269 -- Deprecated django.utils.remove_tag...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e122facbd89c5768528f5ba3b13552d43f989757
  
https://github.com/django/django/commit/e122facbd89c5768528f5ba3b13552d43f989757
  Author: Tim Graham 
  Date:   2014-08-15 (Fri, 15 Aug 2014)

  Changed paths:
M django/utils/html.py
M docs/internals/deprecation.txt
M docs/ref/templates/builtins.txt
M docs/ref/utils.txt
M docs/releases/1.8.txt
M tests/defaultfilters/tests.py
M tests/template_tests/tests.py
M tests/utils_tests/test_html.py

  Log Message:
  ---
  Fixed #23269 -- Deprecated django.utils.remove_tags() and removetags filter.

Also the unused, undocumented django.utils.html.strip_entities() function.


-- 
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/53edfb6a2866d_4e23f8e27e252bc379a5%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22280: "Conflicting models in application" RuntimeError for same model with different paths

[Django]

#22280: "Conflicting models in application" RuntimeError for same model with
different paths
---+
 Reporter:  blueyed|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  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 MalikRumi):

 ROOT_URLCONF = '%s.urls' % SITE_NAME
 SITE_NAME = basename(DJANGO_ROOT)
 DJANGO_ROOT = dirname(dirname(abspath(__file__)))

 url(r'^usconst/', include('usconst.urls')), [this is
 g:\Jasmine\Baillee\Baillee\urls.py]

 urlpatterns = patterns('',
 url(r'^usconst/$',
 apps.usconst.views.catland(template_name='statute.html')),
 url(r'^usconst/Article\s\d[1-5]|[I-V]',
 apps.usconst.views.TOC(template_name='statute.html')),
 url(r'^usconst/Article\s\d[1-5]\s\Section\d[1-5]',
 apps.usconst.views.sectionView(template_name='statute.html')),
 url(r'^usconst/(?P)',
 apps.usconst.views.sectionView(template_name='statute.html')),
 [this is G:\Jasmine\Baillee\Baillee\apps\usconst\urls.py - I noticed a
 missing ' in the regex and fixed it but still got the conflicting names
 error]

 LOCAL_APPS = (
 'apps.usconst.apps.UsconstConfig',
 INSTALLED_APPS = DJANGO_APPS + THIRD_PARTY_APPS + LOCAL_APPS

 G:\Jasmine\Baillee\manage.py

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To 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.4c8406cd9e6d3e1a6238ff17c102d81f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] deed00: Fixed #23162 -- Renamed forms.Field._has_changed()...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: deed00c0d803d324a3dfdeba52458b6b009c1a90
  
https://github.com/django/django/commit/deed00c0d803d324a3dfdeba52458b6b009c1a90
  Author: Gabriel Muñumel 
  Date:   2014-08-15 (Fri, 15 Aug 2014)

  Changed paths:
M django/contrib/auth/forms.py
M django/contrib/auth/tests/test_forms.py
M django/contrib/gis/forms/fields.py
M django/contrib/gis/tests/geoadmin/tests.py
M django/forms/fields.py
M django/forms/forms.py
M django/forms/models.py
M docs/internals/deprecation.txt
M docs/ref/forms/api.txt
M docs/ref/forms/fields.txt
M docs/releases/1.8.txt
M tests/forms_tests/tests/test_extra.py
M tests/forms_tests/tests/test_fields.py

  Log Message:
  ---
  Fixed #23162 -- Renamed forms.Field._has_changed() to has_changed().


-- 
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/53edfa0e85e18_5a903fb6b909d29c424a4%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23162: Rename Field._has_changed() to has_changed()

[Django]

#23162: Rename Field._has_changed() to has_changed()
--+
 Reporter:  timo  |Owner:  gmunumel
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Forms |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 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 ):

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


Comment:

 In [changeset:"deed00c0d803d324a3dfdeba52458b6b009c1a90"]:
 {{{
 #!CommitTicketReference repository=""
 revision="deed00c0d803d324a3dfdeba52458b6b009c1a90"
 Fixed #23162 -- Renamed forms.Field._has_changed() to has_changed().
 }}}

-- 
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.153fd960e64c655454b653912eade17b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23270: select_related on fields pointing to subclasses does not work when using defer

[Django]

#23270: select_related on fields pointing to subclasses does not work when using
defer
-+-
 Reporter:  islavov  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.7-rc-2
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  select_related   |  checkin
  defer  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timgraham):

 * needs_docs:  1 => 0
 * has_patch:  0 => 1
 * type:  Uncategorized => Bug
 * needs_tests:  1 => 0
 * stage:  Accepted => Ready for checkin


Comment:

 Ready for review by ORM experts.

-- 
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.27dc48d3db4bef3812599e46f9f54852%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 23455a: [1.7.x] Fixed typo in docs/howto/custom-model-fiel...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 23455aeee2a9edc71d15d5e15db77fdf641489d9
  
https://github.com/django/django/commit/23455aeee2a9edc71d15d5e15db77fdf641489d9
  Author: Tim Graham 
  Date:   2014-08-15 (Fri, 15 Aug 2014)

  Changed paths:
M docs/howto/custom-model-fields.txt

  Log Message:
  ---
  [1.7.x] Fixed typo in docs/howto/custom-model-fields.txt.

Backport of 99561eef26 from master


-- 
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/53edef6ab0142_60223faf015ad29c76278%40hookshot-fe4-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 99561e: Fixed typo in docs/howto/custom-model-fields.txt.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 99561eef26b75947891929a2b7d5b2c605aa2456
  
https://github.com/django/django/commit/99561eef26b75947891929a2b7d5b2c605aa2456
  Author: Tim Graham 
  Date:   2014-08-15 (Fri, 15 Aug 2014)

  Changed paths:
M docs/howto/custom-model-fields.txt

  Log Message:
  ---
  Fixed typo in docs/howto/custom-model-fields.txt.


-- 
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/53edec8429b80_640f3fbb79d7129c347db%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23293: OSMapWidget.js error when use GeometryCollectionField

[Django]

#23293: OSMapWidget.js error when use GeometryCollectionField
+--
 Reporter:  koyoyo  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  GIS |  Version:  1.6
 Severity:  Normal  |   Resolution:  fixed
 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 claudep):

 * status:  new => closed
 * needs_better_patch:   => 0
 * resolution:   => fixed
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Thanks for the report. I added a fix while backporting other errors
 reported in #23137 ([f5e8376288783554e4da39], 1.7: [2cbafd814f151b8c926],
 master: [12adcd505ebe8159cf4].

-- 
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.bb59abf6df5350f71d83bc5092789299%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23137: Error when use OSMapWidget.js

[Django]

#23137: Error when use OSMapWidget.js
+
 Reporter:  koyoyo  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  GIS |  Version:  1.6
 Severity:  Normal  |   Resolution:  fixed
 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 claudep):

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


Comment:

 OK, thanks for the feedback. Backported in 1.6 in
 [f5e8376288783554e4da39].

-- 
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.f06d9e8f847316bea845db2f85b9a37d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 12adcd: Complemented 1.6 release notes for 457c16d0d6

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 12adcd505ebe8159cf4644cfa8d393b15ca9d5ea
  
https://github.com/django/django/commit/12adcd505ebe8159cf4644cfa8d393b15ca9d5ea
  Author: Claude Paroz 
  Date:   2014-08-15 (Fri, 15 Aug 2014)

  Changed paths:
M django/contrib/gis/static/gis/js/OLMapWidget.js
M docs/releases/1.6.6.txt

  Log Message:
  ---
  Complemented 1.6 release notes for 457c16d0d6

And accessorily added missing bits fixing #23293.
Forward port of 2cbafd814 from stable/1.7.x


-- 
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/53edc19ee2fec_631c3fe4ace7d29c328af%40hookshot-fe4-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 2cbafd: [1.7.x] Complemented 1.6 release notes for 457c16d...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 2cbafd814f151b8c926ed8a955627edb8ea23b23
  
https://github.com/django/django/commit/2cbafd814f151b8c926ed8a955627edb8ea23b23
  Author: Claude Paroz 
  Date:   2014-08-15 (Fri, 15 Aug 2014)

  Changed paths:
M django/contrib/gis/static/gis/js/OLMapWidget.js
M docs/releases/1.6.6.txt

  Log Message:
  ---
  [1.7.x] Complemented 1.6 release notes for 457c16d0d6

And accessorily added missing bits fixing #23293.


-- 
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/53edc1611e067_8eb3fbf8c1e329c91183%40hookshot-fe3-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] f5e837: [1.6.x] Fixed multi geometries editing in OpenLaye...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: f5e8376288783554e4da398183dfa627c73401e5
  
https://github.com/django/django/commit/f5e8376288783554e4da398183dfa627c73401e5
  Author: Claude Paroz 
  Date:   2014-08-15 (Fri, 15 Aug 2014)

  Changed paths:
M django/contrib/gis/static/gis/js/OLMapWidget.js
M docs/releases/1.6.6.txt

  Log Message:
  ---
  [1.6.x] Fixed multi geometries editing in OpenLayers widget

Backport of 457c16d0d from master.


-- 
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/53edc08022381_56ce3fdb88e3d2a019712%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21173: Django DateTimeInput determines language/locale at startup time but this may change later, resulting in validation errors

[Django]

#21173: Django DateTimeInput determines language/locale at startup time but this
may change later, resulting in validation errors
-+-
 Reporter:  django-locale-   |Owner:  claudep
  issue@…|   Status:  closed
 Type:  Bug  |  Version:  master
Component:  Forms|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
  forms,widgets,locale   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by mbertheau):

 Any chance this makes it into 1.6? It's a pretty serious issue where the
 user accessing the page with a different language preference breaks
 date(time) fields in all forms.

-- 
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/087.eac1b22b1da2ab0a8a48a4814afba7ca%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.