Re: [Django] #28101: Regression in nested __in subquery lookups when using to_field.

[Django]

#28101: Regression in nested __in subquery lookups when using to_field.
-+-
 Reporter:  Kristian Klette  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette ):

 In [changeset:"0ad16934940fdbf0984f5255c7e5fff085593737" 0ad16934]:
 {{{
 #!CommitTicketReference repository=""
 revision="0ad16934940fdbf0984f5255c7e5fff085593737"
 [1.11.x] Fixed #28101 -- Fixed a regression with nested __in subquery
 lookups and to_field.

 Thanks Kristian Klette for the report and Tim for the help.

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

Re: [Django] #28101: Regression in nested __in subquery lookups when using to_field.

[Django]

#28101: Regression in nested __in subquery lookups when using to_field.
-+-
 Reporter:  Kristian Klette  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette ):

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


Comment:

 In [changeset:"8ef35468b660e1c25af67a8299202b8bc108679f" 8ef35468]:
 {{{
 #!CommitTicketReference repository=""
 revision="8ef35468b660e1c25af67a8299202b8bc108679f"
 Fixed #28101 -- Fixed a regression with nested __in subquery lookups and
 to_field.

 Thanks Kristian Klette for the report and Tim for the help.
 }}}

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

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

Re: [Django] #28101: Regression in nested __in subquery lookups when using to_field.

[Django]

#28101: Regression in nested __in subquery lookups when using to_field.
-+-
 Reporter:  Kristian Klette  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #28101: Regression in nested __in subquery lookups when using to_field. (was: #26196 regression - __in lookups don't honor to_field)

[Django]

#28101: Regression in nested __in subquery lookups when using to_field.
-+-
 Reporter:  Kristian Klette  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Release blocker  |   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 Simon Charette):

 * has_patch:  0 => 1


Comment:

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

 Kristian, could you confirm the proposed patch solves your issue? Thanks.

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

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

Re: [Django] #28099: Reuse of UpdateQuery breaks complex delete updates

[Django]

#28099: Reuse of UpdateQuery breaks complex delete updates
-+-
 Reporter:  milosu   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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

Re: [Django] #28099: Reuse of UpdateQuery breaks complex delete updates

[Django]

#28099: Reuse of UpdateQuery breaks complex delete updates
-+-
 Reporter:  milosu   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_better_patch:  0 => 1


Comment:

 I haven't investigated this is detail but it would be nice to understand
 the root cause of the issue a bit more to confirm that the fix is the best
 one. The patch should be reworked to apply to master (which supports
 Python 3 only) and the test simplified as much as possible. Existing test
 models should be used as much as possible. If any new models are needed
 they should have as few fields as possible. The test should use `create()`
 rather than `get_or_create()` and I don' think the `DoesNotExist`
 exception catching is necessary.

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

Re: [Django] #28115: geoip2 module broken with ImportError on master

[Django]

#28115: geoip2 module broken with ImportError on master
-+-
 Reporter:  Claude Paroz |Owner:  Claude
 |  Paroz
 Type:  Bug  |   Status:  assigned
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"257075d4adf9ce0fae8ca1ec3c680dc071fa5a72" 257075d4]:
 {{{
 #!CommitTicketReference repository=""
 revision="257075d4adf9ce0fae8ca1ec3c680dc071fa5a72"
 Refs #28115 -- Avoided masking legitimate ImportErrors in geoip2 module
 }}}

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

Re: [Django] #28115: geoip2 module broken with ImportError on master

[Django]

#28115: geoip2 module broken with ImportError on master
-+-
 Reporter:  Claude Paroz |Owner:  Claude
 |  Paroz
 Type:  Bug  |   Status:  closed
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"3f1ba76851e1dc140d4544fa50a463425be197b2" 3f1ba768]:
 {{{
 #!CommitTicketReference repository=""
 revision="3f1ba76851e1dc140d4544fa50a463425be197b2"
 Fixed #28115 -- Fixed IP address validation in geoip2 module

 Regression in 277a4dd4b4cc2a2cad77139882f084480751a95a.
 Thanks Tim Graham for the test.
 }}}

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

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

Re: [Django] #28109: Paginator warning about unordered object list should have the appropriate stacklevel

[Django]

#28109: Paginator warning about unordered object list should have the 
appropriate
stacklevel
-+-
 Reporter:  Simon Charette   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:  1.11
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette ):

 In [changeset:"395df007f4151390c614866d99827bbed1795a43" 395df007]:
 {{{
 #!CommitTicketReference repository=""
 revision="395df007f4151390c614866d99827bbed1795a43"
 [1.11.x] Fixed #28109 -- Corrected the stack level of unordered queryset
 pagination warnings.

 Refs #26290.

 Thanks Tim for the review.

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

Re: [Django] #26290: Pagination module should warn about unordered query set

[Django]

#26290: Pagination module should warn about unordered query set
-+-
 Reporter:  Kartik Anand |Owner:  Tim
 Type:   |  Graham 
  Cleanup/optimization   |   Status:  closed
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  pagination   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette ):

 In [changeset:"395df007f4151390c614866d99827bbed1795a43" 395df007]:
 {{{
 #!CommitTicketReference repository=""
 revision="395df007f4151390c614866d99827bbed1795a43"
 [1.11.x] Fixed #28109 -- Corrected the stack level of unordered queryset
 pagination warnings.

 Refs #26290.

 Thanks Tim for the review.

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

Re: [Django] #28109: Paginator warning about unordered object list should have the appropriate stacklevel

[Django]

#28109: Paginator warning about unordered object list should have the 
appropriate
stacklevel
-+-
 Reporter:  Simon Charette   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:  1.11
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette ):

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


Comment:

 In [changeset:"c0f12a098c0258eef3e9af982c17f5ef7f6c927d" c0f12a0]:
 {{{
 #!CommitTicketReference repository=""
 revision="c0f12a098c0258eef3e9af982c17f5ef7f6c927d"
 Fixed #28109 -- Corrected the stack level of unordered queryset pagination
 warnings.

 Refs #26290.

 Thanks Tim for the review.
 }}}

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

Re: [Django] #26290: Pagination module should warn about unordered query set

[Django]

#26290: Pagination module should warn about unordered query set
-+-
 Reporter:  Kartik Anand |Owner:  Tim
 Type:   |  Graham 
  Cleanup/optimization   |   Status:  closed
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  pagination   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette ):

 In [changeset:"c0f12a098c0258eef3e9af982c17f5ef7f6c927d" c0f12a0]:
 {{{
 #!CommitTicketReference repository=""
 revision="c0f12a098c0258eef3e9af982c17f5ef7f6c927d"
 Fixed #28109 -- Corrected the stack level of unordered queryset pagination
 warnings.

 Refs #26290.

 Thanks Tim for the review.
 }}}

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

Re: [Django] #27881: Add "unified diff" output mode to diffsettings management command

[Django]

#27881: Add "unified diff" output mode to diffsettings management command
-+-
 Reporter:  Chris Lamb   |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_docs:  1 => 0


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

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

Re: [Django] #28115: geoip2 module broken with ImportError on master (was: geoip2 module broken on master)

[Django]

#28115: geoip2 module broken with ImportError on master
-+-
 Reporter:  Claude Paroz |Owner:  Claude
 |  Paroz
 Type:  Bug  |   Status:  assigned
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * stage:  Accepted => Ready for checkin


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

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

[Django] #28117: loaddata raises ValueError with psycopg2 backend

[Django]

#28117: loaddata raises ValueError with psycopg2 backend
-+-
   Reporter:  Nicolas|  Owner:  nobody
  Kuttler|
   Type: | Status:  new
  Cleanup/optimization   |
  Component:  Core   |Version:  1.11
  (Management commands)  |
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I have a site that currently uses mysql. The `admin.logentry` table
 contains `object_repr` values from spam submissions like

 `\u589f0\u0005\u0001\u\u: Nice article`

 While migrating the site to postgres importing fixtures created with
 dumpdata raises a `ValueError` originating in (I think)
 https://github.com/psycopg/psycopg2/blob/2_7_1/psycopg/utils.c#L58 and not
 handled in
 
https://github.com/django/django/blob/stable/1.11.x/django/core/management/commands/loaddata.py#L181

 One possible fix, to give users a more informative error message, would be
 to catch ValueErrors as well on that line.

 {{{
 Traceback (most recent call last):
   File "./src/manage.py", line 8, in 
 execute_from_command_line(sys.argv)
   File
 "/srv/www/project/staging/20170422-113847/virtualenv/local/lib/python2.7
 /site-packages/django/core/management/__init__.py", line 367, in
 execute_from_command_line
 utility.execute()
   File
 "/srv/www/project/staging/20170422-113847/virtualenv/local/lib/python2.7
 /site-packages/django/core/management/__init__.py", line 359, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File
 "/srv/www/project/staging/20170422-113847/virtualenv/local/lib/python2.7
 /site-packages/django/core/management/base.py", line 294, in run_from_argv
 self.execute(*args, **cmd_options)
   File
 "/srv/www/project/staging/20170422-113847/virtualenv/local/lib/python2.7
 /site-packages/django/core/management/base.py", line 345, in execute
 output = self.handle(*args, **options)
   File
 "/srv/www/project/staging/20170422-113847/virtualenv/local/lib/python2.7
 /site-packages/django/core/management/commands/loaddata.py", line 64, in
 handle
 self.loaddata(fixture_labels)
   File
 "/srv/www/project/staging/20170422-113847/virtualenv/local/lib/python2.7
 /site-packages/django/core/management/commands/loaddata.py", line 104, in
 loaddata
 self.load_label(fixture_label)
   File
 "/srv/www/project/staging/20170422-113847/virtualenv/local/lib/python2.7
 /site-packages/django/core/management/commands/loaddata.py", line 167, in
 load_label
 obj.save(using=self.using)
   File
 "/srv/www/project/staging/20170422-113847/virtualenv/local/lib/python2.7
 /site-packages/django/core/serializers/base.py", line 201, in save
 models.Model.save_base(self.object, using=using, raw=True, **kwargs)
   File
 "/srv/www/project/staging/20170422-113847/virtualenv/local/lib/python2.7
 /site-packages/django/db/models/base.py", line 824, in save_base
 updated = self._save_table(raw, cls, force_insert, force_update,
 using, update_fields)
   File
 "/srv/www/project/staging/20170422-113847/virtualenv/local/lib/python2.7
 /site-packages/django/db/models/base.py", line 889, in _save_table
 forced_update)
   File
 "/srv/www/project/staging/20170422-113847/virtualenv/local/lib/python2.7
 /site-packages/django/db/models/base.py", line 939, in _do_update
 return filtered._update(values) > 0
   File
 "/srv/www/project/staging/20170422-113847/virtualenv/local/lib/python2.7
 /site-packages/django/db/models/query.py", line 654, in _update
 return query.get_compiler(self.db).execute_sql(CURSOR)
   File
 "/srv/www/project/staging/20170422-113847/virtualenv/local/lib/python2.7
 /site-packages/django/db/models/sql/compiler.py", line 1148, in
 execute_sql
 cursor = super(SQLUpdateCompiler, self).execute_sql(result_type)
   File
 "/srv/www/project/staging/20170422-113847/virtualenv/local/lib/python2.7
 /site-packages/django/db/models/sql/compiler.py", line 835, in execute_sql
 cursor.execute(sql, params)
   File
 "/srv/www/project/staging/20170422-113847/virtualenv/local/lib/python2.7
 /site-packages/django/db/backends/utils.py", line 64, in execute
 return self.cursor.execute(sql, params)
 ValueError: Problem installing fixture '/srv/www/project/data.json': A
 string literal cannot contain NUL (0x00) characters.
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/28117>
Django <https://c

Re: [Django] #28116: Filtering PostgreSQL exception based on message is too brittle

[Django]

#28116: Filtering PostgreSQL exception based on message is too brittle
-+-
 Reporter:  Claude Paroz |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz):

 What about just trying to check if the database exists when `keepdb` is
 True?

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

Re: [Django] #28116: Filtering PostgreSQL exception based on message is too brittle

[Django]

#28116: Filtering PostgreSQL exception based on message is too brittle
-+-
 Reporter:  Claude Paroz |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 felixxm):

 * owner:  nobody => felixxm
 * status:  new => assigned
 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #28116: Filtering PostgreSQL exception based on message is too brittle

[Django]

#28116: Filtering PostgreSQL exception based on message is too brittle
-+-
 Reporter:  Claude Paroz |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz):

 * cc: felixxm (added)


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

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

[Django] #28116: Filtering PostgreSQL exception based on message is too brittle

[Django]

#28116: Filtering PostgreSQL exception based on message is too brittle
-+-
   Reporter:  Claude |  Owner:  nobody
  Paroz  |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  master
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 In commit 64264c9a19b7dae6cd1d5e112177cdbcafafc93c, the behavior of
 `_execute_create_test_db` depends on the databae error message `''database
 %s already exists'`.

 On my system for example, the error message is localized so I'm finally
 getting a message `Got an error creating the test database: la base de
 données « test_testgis1 » existe déjà` even when I provide `--keepdb`.

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

Re: [Django] #28115: geoip2 module broken on master

[Django]

#28115: geoip2 module broken on master
--+
 Reporter:  Claude Paroz  |Owner:  Claude Paroz
 Type:  Bug   |   Status:  assigned
Component:  GIS   |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Claude Paroz):

 * has_patch:  0 => 1


Comment:

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

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

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

Re: [Django] #26423: Make EmailValidator use HTML5 validation rather than more complicated regular expressions

[Django]

#26423: Make EmailValidator use HTML5 validation rather than more complicated
regular expressions
--+
 Reporter:  Tim Graham|Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Haris Ibrahim K. V.):

 * status:  assigned => new
 * owner:  Haris Ibrahim K. V. => (none)


Comment:

 Not maintaining the PR any more. Please do feel free to fork and submit a
 new PR.

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

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

Re: [Django] #27881: Add "unified diff" output mode to diffsettings management command

[Django]

#27881: Add "unified diff" output mode to diffsettings management command
-+-
 Reporter:  Chris Lamb   |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Haris Ibrahim K. V.):

 * status:  assigned => new
 * owner:  Haris Ibrahim K. V. => (none)


Comment:

 Not maintaining the PR any more. Please do feel free to fork and submit a
 new PR.

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

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

[Django] #28115: geoip2 module broken on master

[Django]

#28115: geoip2 module broken on master
+--
   Reporter:  Claude Paroz  |  Owner:  Claude Paroz
   Type:  Bug   | Status:  assigned
  Component:  GIS   |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+--
 The geoip2 module is currently broken because it can't import
 `django.core.validators.ipv4_re`.
 The breakage was my commit 277a4dd4b4cc2a2cad77139882f084480751a95a.

 The `ImportError` catching in the `__init__` file is currently not
 specific enough to catch those failures.

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

Re: [Django] #28114: Using a custom user model when starting a project: default code generation.

[Django]

#28114: Using a custom user model when starting a project: default code 
generation.
-+-
 Reporter:  RichardProsser   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  1.11
  commands)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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


Comment:

 Duplicate of #27909.

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

Re: [Django] #28100: Remove link in UserChangeForm.password's translatable help_text

[Django]

#28100: Remove link in UserChangeForm.password's translatable help_text
-+-
 Reporter:  Hélio Correia|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"c52ae33a0c0c0bbaa460607a8787e95fe983a2b9" c52ae33a]:
 {{{
 #!CommitTicketReference repository=""
 revision="c52ae33a0c0c0bbaa460607a8787e95fe983a2b9"
 Fixed #28100 -- Removed link in UserChangeForm.password's translatable
 help_text
 }}}

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

Re: [Django] #3461: DatabaseWrapper should pass through args and kwargs to underlying database adapter

[Django]

#3461: DatabaseWrapper should pass through args and kwargs to underlying 
database
adapter
-+-
 Reporter:  Jack Moffitt |Owner:  Asif
     |  Saifuddin Auvi
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Asif Saifuddin Auvi):

 * needs_docs:  0 => 1


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

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

Re: [Django] #5929: Allow Fields to use multiple db columns (complex datatypes)

[Django]

#5929: Allow Fields to use multiple db columns (complex datatypes)
-+-
 Reporter:  Daniel   |Owner:  (none)
  Poelzleithner  |
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 Asif Saifuddin Auvi):

 Replying to [comment:25 Collin Anderson]:
 > This should be much easier now that the _meta refactor is complete.

 any work around?

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

Re: [Django] #28103: Add "quarter" lookup to DateField/DateTimeField

[Django]

#28103: Add "quarter" lookup to DateField/DateTimeField
-+-
 Reporter:  Matthew Pava |Owner:  Mads
 |  Jensen
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ORM Extract Trunc| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mads Jensen):

 Oracle and PostgreSQL have built-in functionality for truncating a date to
 the first month of a quarter. However, in Oracle, it rounds up
 (https://docs.oracle.com/database/121/SQLRF/functions271.htm#SQLRF52058)
 and in PostgreSQL, it's always rounded down
 (https://www.postgresql.org/docs/current/static/functions-datetime.html
 #FUNCTIONS-DATETIME-TRUNC). Neither SQLite or MySQL has a convenient
 built-in functionality and it's a matter of interpretation.

 The Extract functionality is implemented, and has the same behavior on all
 backends.

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

[Django] #28114: Using a custom user model when starting a project: default code generation.

[Django]

#28114: Using a custom user model when starting a project: default code 
generation.
-+-
   Reporter: |  Owner:  nobody
  RichardProsser |
   Type:  New| Status:  new
  feature|
  Component:  Core   |Version:  1.11
  (Management commands)  |
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 https://docs.djangoproject.com/en/1.11/topics/auth/customizing/#using-a
 -custom-user-model-when-starting-a-project: "If you’re starting a new
 project, it’s highly recommended to set up a custom user model, even if
 the default User model is sufficient for you".

 If that is the case, surely it would be better to generate such code by
 default, via 'django-admin startapp' or the like?

 I am fairly new to Django and I nearly missed this point for my own
 application.


 Regards,

 Richard

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