Re: [Django] #28459: Improve performance of QuerySet

[Django]

#28459: Improve performance of QuerySet
-+-
 Reporter:  Sergey Fedoseev  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Sergey Fedoseev):

 [https://github.com/django/django/pull/9494 PR (Improved performance of
 loading DurationField on SQLite and MySQL.)]

 Before:
 {{{
 %timeit for x in DurationModel.objects.values_list('d'): pass
 168 ms ± 678 µs per loop (mean ± std. dev. of 7 runs, 10 loops each)
 }}}
 After:
 {{{
 %timeit for x in DurationModel.objects.values_list('d'): pass
 23.1 ms ± 243 µs per loop (mean ± std. dev. of 7 runs, 10 loops each)
 }}}

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

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

[Django] #28966: GUID without "-" is not recognized by url path

[Django]

#28966: GUID without "-" is not recognized by url path
---+
   Reporter:  Jahongir |  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  Core (URLs)  |Version:  2.0
   Severity:  Normal   |   Keywords:  urls
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 I have this url path:

 path('driver//logs/', views.LogListView.as_view(),
 name='list-logs'),

 If I try this: `reverse('list-logs', kwargs={'driver_guid':
 '3d2dde2ef06d465283c8849e9eba7bae'})`, it does not find the path because
 the guid does not have '-'.

 If I try `reverse('list-logs', kwargs={'driver_guid': '3d2dde2e-
 f06d-4652-83c8-849e9eba7bae'})` it does work.

 The problem is that `3d2dde2ef06d465283c8849e9eba7bae` is also a valid
 uuid.

 I think it should be recognized as well.

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

Re: [Django] #28964: RenameField after AddField after CreateModel in one operations list gives ProgrammingError: relation "field" does not exist

[Django]

#28964: RenameField after AddField after CreateModel in one operations list 
gives
ProgrammingError: relation "field" does not exist
--+--
 Reporter:  Matthew Pava  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Migrations|  Version:  1.11
 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 Simon Charette):

 If you get the `ProgrammingError` during index or foreign key constraint
 creation than I'm fairly confident this is a duplicate of #25530 which is
 fixed in Django 2.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/064.1e242d881ec7d91ec7e6bddd26094fec%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28964: RenameField after AddField after CreateModel in one operations list gives ProgrammingError: relation "field" does not exist

[Django]

#28964: RenameField after AddField after CreateModel in one operations list 
gives
ProgrammingError: relation "field" does not exist
--+--
 Reporter:  Matthew Pava  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Migrations|  Version:  1.11
 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 Matthew Pava):

 Not at the moment with my particular project, though I have tried.  (I'm
 waiting for a 3rd-party package to get Django 2.0 support.)  I will
 continue trying tomorrow, but I will state that I'm getting different
 results than with Django 1.11.  There are still some bugs I'm seeing, but
 I haven't determined conclusively if they are related to the migrations.

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

Re: [Django] #28459: Improve performance of QuerySet

[Django]

#28459: Improve performance of QuerySet
-+-
 Reporter:  Sergey Fedoseev  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"d0f569b350bca89eeb186523d8905a6e31b5a947" d0f569b3]:
 {{{
 #!CommitTicketReference repository=""
 revision="d0f569b350bca89eeb186523d8905a6e31b5a947"
 Refs #28459 -- Improved performance of loading DecimalField on SQLite.
 }}}

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

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

Re: [Django] #28964: RenameField after AddField after CreateModel in one operations list gives ProgrammingError: relation "field" does not exist

[Django]

#28964: RenameField after AddField after CreateModel in one operations list 
gives
ProgrammingError: relation "field" does not exist
--+--
 Reporter:  Matthew Pava  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Migrations|  Version:  1.11
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by Tim Graham):

 Can you test with Django 2.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/064.c8b7d780a8835261029b3d399ff2aec8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28965: Wrong format for cookie 'expires'

[Django]

#28965: Wrong format for cookie 'expires'
---+--
 Reporter:  Alexey |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Utilities  |  Version:  2.0
 Severity:  Normal |   Resolution:
 Keywords:  cookie | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by Tim Graham):

 Are you seeing a problematic behavior or is this merely cosmetic?

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

Re: [Django] #28928: Add support for expression indexes for GinIndex (was: Support expression indexes for GinIndex)

[Django]

#28928: Add support for expression indexes for GinIndex
--+
 Reporter:  James Howe|Owner:  (none)
 Type:  New feature   |   Status:  new
Component:  contrib.postgres  |  Version:  1.11
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham):

 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #28930: Simplify code with all() and any()

[Django]

#28930: Simplify code with all() and any()
-+-
 Reporter:  Дилян Палаузов   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"4c599ece57fa009cf3615f09497f81bfa6a585a7" 4c599ece]:
 {{{
 #!CommitTicketReference repository=""
 revision="4c599ece57fa009cf3615f09497f81bfa6a585a7"
 Fixed #28930 -- Simplified code with any() and all().
 }}}

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

Re: [Django] #28965: Wrong format for cookie 'expires'

[Django]

#28965: Wrong format for cookie 'expires'
---+--
 Reporter:  Alexey |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Utilities  |  Version:  2.0
 Severity:  Normal |   Resolution:
 Keywords:  cookie | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Description changed by Alexey:

Old description:

> For some reason Django set expires for cookies with slashes in date.
>
> Seems it was first introduced in
> [https://github.com/django/django/commit/390666ac2bf8223bede4f78a97836051bc9f9526
> 390666ac2bf8223bede4f78a97836051bc9f9526] to fix #508
>
> The proper format is UTC string (RFC-1123)

New description:

 For some reason Django set expires for cookies with hyphens in date (Tue,
 25-Dec-2018 22:26:13 GMT).

 Seems it was first introduced in
 
[https://github.com/django/django/commit/390666ac2bf8223bede4f78a97836051bc9f9526
 390666ac2bf8223bede4f78a97836051bc9f9526] to fix #508

 The proper format is UTC string (RFC-1123): Tue, 25 Dec 2018 21:15:29 GMT

--

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

[Django] #28965: Wrong format for cookie 'expires'

[Django]

#28965: Wrong format for cookie 'expires'
--+
   Reporter:  Alexey  |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  Utilities   |Version:  2.0
   Severity:  Normal  |   Keywords:  cookie
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  1
  UI/UX:  0   |
--+
 For some reason Django set expires for cookies with slashes in date.

 Seems it was first introduced in
 
[https://github.com/django/django/commit/390666ac2bf8223bede4f78a97836051bc9f9526
 390666ac2bf8223bede4f78a97836051bc9f9526] to fix #508

 The proper format is UTC string (RFC-1123)

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

[Django] #28964: RenameField after AddField after CreateModel in one operations list gives ProgrammingError: relation "field" does not exist

[Django]

#28964: RenameField after AddField after CreateModel in one operations list 
gives
ProgrammingError: relation "field" does not exist
+
   Reporter:  Matthew Pava  |  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  Migrations|Version:  1.11
   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 |
+
 In one migration file, I have this series of operations:


 {{{
 migrations.CreateModel(m, fields=[a, b, c])
 migrations.AddField(m, x)
 migrations.RenameField(x, y)
 }}}


 I get this:
 {{{
  ProgrammingError: column "x_id" does not exist.
 }}}


 I workaround it by replacing x with y in the `AddField` operation and then
 removing the `RenameField` operation.

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

Re: [Django] #28962: Documentation of use of template tags in forms

[Django]

#28962: Documentation of use of template tags in forms
-+-
 Reporter:  Malik A. Rumi|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  forms,   | Triage Stage:
  templatetags, urls |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham):

 I guess you're referring to an example like:
 {{{
 @permission_required('polls.can_vote', login_url='/loginpage/')
 }}}
 which instead could be something like (untested):
 {{{
 @permission_required('polls.can_vote', login_url=reverse_lazy('some-page-
 nam'`))
 }}}
 (I think you mixed up terminology in calling `reverse()` and
 `reverse_lazy()` "template tags"... probably you were thinking of the {%
 url %} tag.)

 I don't know if we should try to avoid hardcoding URLs in all examples. It
 may make things a bit less readable. Nor am I sure if it's beneficial to
 mention everywhere a URL is accepted that you can also use `reverse()` to
 avoid hardcoding one. The topic of hardcoding URLs is discussed in the
 tutorial, so hopefully a Django user would remember that and not need a
 constant reminder.

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

Re: [Django] #28930: Simplify code with all() and any() (was: Simplify code iwth all() and any())

[Django]

#28930: Simplify code with all() and any()
-+-
 Reporter:  Дилян Палаузов   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Other) |  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
-+-

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

Re: [Django] #28930: Simplify code iwth all() and any() (was: Utilize all()/any())

[Django]

#28930: Simplify code iwth all() and any()
-+-
 Reporter:  Дилян Палаузов   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Other) |  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):

 * has_patch:  0 => 1
 * component:  Uncategorized => Core (Other)
 * stage:  Accepted => Ready for checkin


Comment:

 That's fine. For future reference, the way to credit the patch author is
 using `git commit --amend --author="Дилян Палаузов
 "`. It would have been nice if you fixed up the
 flake8 issues and the failing lists, but I've done that. I also reverted
 changes to vendored code like `six.py` and an incorrect change in
 `admin/utils.py` which changed behavior and broke a test.

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

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

Re: [Django] #28949: Multibyte table name or column name causes miscalculation of the length of index name.

[Django]

#28949: Multibyte table name or column name causes miscalculation of the length 
of
index name.
-+-
 Reporter:  Pak Youngrok |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  migration multibyte  | Triage Stage:  Accepted
  index  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #28930: Utilize all()/any()

[Django]

#28930: Utilize all()/any()
--+
 Reporter:  Дилян Палаузов|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Uncategorized |  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
--+

Old description:

> What is the policy for taking  this patch and raising a PR? Ofcourse, I
> acknowledge the author.
>
> I like this patch very much, i couldn't resist to raise a PR.  If i break
> the unspoken rules, please close the PR.
>
> https://github.com/django/django/pull/9493

New description:



--

Comment (by Srinivas Reddy Thatiparthy):

 What is the policy for taking  this patch and raising a PR? Ofcourse, I
 acknowledge the author.

 I like this patch very much, i couldn't resist to raise a PR.  If i break
 the unspoken rules, please close the PR.

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

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

Re: [Django] #28930: Utilize all()/any()

[Django]

#28930: Utilize all()/any()
--+
 Reporter:  Дилян Палаузов|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Uncategorized |  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
--+
Description changed by Srinivas Reddy Thatiparthy:

Old description:



New description:

 What is the policy for taking  this patch and raising a PR? Ofcourse, I
 acknowledge the author.

 I like this patch very much, i couldn't resist to raise a PR.  If i break
 the unspoken rules, please close the PR.

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

--

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

Re: [Django] #28944: Chaining values()/values_list() after QuerySet.select_for_update(of=()) crashes

[Django]

#28944: Chaining values()/values_list() after QuerySet.select_for_update(of=())
crashes
-+-
 Reporter:  Thierry Bastian  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.0
  (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 Tim Graham ):

 In [changeset:"4e4619a2b8f79699fbdb2c4f1bc4db55f59af6e6" 4e4619a]:
 {{{
 #!CommitTicketReference repository=""
 revision="4e4619a2b8f79699fbdb2c4f1bc4db55f59af6e6"
 [2.0.x] Fixed #28944 -- Fixed crash when chaining values()/values_list()
 after QuerySet.select_for_update(of=()).

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

Re: [Django] #28783: Support for custom operator class for indexes

[Django]

#28783: Support for custom operator class for indexes
-+-
 Reporter:  vinay karanam|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  postgres, operator   | Triage Stage:
  class  |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 Is there a need for a separate ticket from #28077? (Is there some
 additional work needed to close that or could we just retitle it?)

 I'm unsure if adding database-specific kwargs like `operator_class` to
 `Index.__init__()` is a good approach, but I don't have an alternative in
 mind.

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

Re: [Django] #28944: Chaining values()/values_list() after QuerySet.select_for_update(of=()) crashes

[Django]

#28944: Chaining values()/values_list() after QuerySet.select_for_update(of=())
crashes
-+-
 Reporter:  Thierry Bastian  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.0
  (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 Tim Graham ):

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


Comment:

 In [changeset:"c21f158295d92e35caf96436bfdbbff554fc5569" c21f1582]:
 {{{
 #!CommitTicketReference repository=""
 revision="c21f158295d92e35caf96436bfdbbff554fc5569"
 Fixed #28944 -- Fixed crash when chaining values()/values_list() after
 QuerySet.select_for_update(of=()).
 }}}

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

Re: [Django] #28950: ArrayField.has_changed() returns True for unchanged fields (was: Model with OnetoOneFeild inline in admin cannot be created)

[Django]

#28950: ArrayField.has_changed() returns True for unchanged fields
--+
 Reporter:  tejinderss|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.postgres  |  Version:  1.11
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham):

 * component:  Uncategorized => contrib.postgres
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

 The problem is `ArrayField.has_changed()` returning `True` even though the
 field wasn't modified.

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

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

Re: [Django] #28961: Convert result of predicate in the function django.utils.functional.partition to bool

[Django]

#28961: Convert result of predicate in the function
django.utils.functional.partition to bool
-+-
 Reporter:  Vitaliy  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Utilities|  Version:  1.11
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  functional   | Triage Stage:
  partition  |  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:   => wontfix


Comment:

 `partition()` isn't a documented function and I don't see a strong reason
 to add logic to it that Django's usage doesn't require.

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

Re: [Django] #28959: Clicking "No, take me back" on the delete selected inline foreign key / one-to-one field confirmation page does nothing (was: Canceling removing inline Foreign Key does not work)

[Django]

#28959: Clicking "No, take me back" on the delete selected inline foreign key /
one-to-one field confirmation page does nothing
---+
 Reporter:  Josh Schneier  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  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 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/067.8c517c5af2d08e70ee9690910c7c586f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28731: Passing an empty Q() to a When inside a Case causes an OperationError

[Django]

#28731: Passing an empty Q() to a When inside a Case causes an OperationError
-+-
 Reporter:  Tom van Bussel   |Owner:  Tim
 |  Martin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"5778b5701d6a0feb3053b70891cd8ce80b6e8601" 5778b57]:
 {{{
 #!CommitTicketReference repository=""
 revision="5778b5701d6a0feb3053b70891cd8ce80b6e8601"
 Fixed #28731 -- Added an error message when using an empty Q() in a When
 expression.

 Otherwise it generates invalid SQL.
 }}}

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

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

Re: [Django] #28956: Update admin's jQuery to 3.2.1

[Django]

#28956: Update admin's jQuery to 3.2.1
-+-
 Reporter:  Tim Graham   |Owner:  Tim
 Type:   |  Graham
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"0fc4b1f31f3cf7788e38a3d53f32254d340f50e8" 0fc4b1f3]:
 {{{
 #!CommitTicketReference repository=""
 revision="0fc4b1f31f3cf7788e38a3d53f32254d340f50e8"
 Refs #28956 -- Removed usage of jQuery's deprecated event methods in admin
 JavaScript.
 }}}

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

Re: [Django] #28956: Update admin's jQuery to 3.2.1

[Django]

#28956: Update admin's jQuery to 3.2.1
-+-
 Reporter:  Tim Graham   |Owner:  Tim
 Type:   |  Graham
  Cleanup/optimization   |   Status:  closed
Component:  contrib.admin|  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:"6deaddcca367d0143c815aaa42342021baa3b41e" 6deaddcc]:
 {{{
 #!CommitTicketReference repository=""
 revision="6deaddcca367d0143c815aaa42342021baa3b41e"
 Fixed #28956 -- Updated admin's jQuery to 3.2.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/067.72c201cae5d866b099a95b5541fdc02a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28956: Update admin's jQuery to 3.2.1

[Django]

#28956: Update admin's jQuery to 3.2.1
-+-
 Reporter:  Tim Graham   |Owner:  Tim
 Type:   |  Graham
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"b730973fff14f4e0184f5522eaf9f5e64891d431" b730973f]:
 {{{
 #!CommitTicketReference repository=""
 revision="b730973fff14f4e0184f5522eaf9f5e64891d431"
 Refs #28956 -- Removed usage of jQuery's deprecated .selector property in
 admin JavaScript.
 }}}

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

Re: [Django] #28961: Convert result of predicate in the function django.utils.functional.partition to bool (was: Convert result of the predicate in the function django.utils.functional.partition to bo

[Django]

#28961: Convert result of predicate in the function
django.utils.functional.partition to bool
-+-
 Reporter:  Vitaliy  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Utilities|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  functional   | Triage Stage:
  partition  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

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

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

Re: [Django] #28958: Admin changelist crashes when using query expression in the model's Meta.ordering or ModelAdmin.ordering

[Django]

#28958: Admin changelist crashes when using query expression in the model's
Meta.ordering or ModelAdmin.ordering
-+-
 Reporter:  Gabriel Amram|Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  2.0
 Severity:  Release blocker  |   Resolution:
 Keywords:  query expresssion,   | Triage Stage:  Accepted
  ordering, admin, meta  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/9491 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/071.235821548a235de82cebed62bb94eba1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.