Re: [Django] #33407: Radiolist etc. styling has changed since it's using div elements not ul elements

2022-01-25 Thread Django
#33407: Radiolist etc. styling has changed since it's using div elements not ul
elements
-+-
 Reporter:  Matthias Kestenholz  |Owner:  Carlton
 |  Gibson
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  4.0
 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 Mariusz Felisiak):

 * stage:  Accepted => Ready for checkin


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

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


Re: [Django] #28919: Add support for Common Table Expression (CTE) queries

2022-01-25 Thread Django
#28919: Add support for Common Table Expression (CTE) queries
-+-
 Reporter:  Daniel Miller|Owner:  Moses
 |  Mugisha
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  QuerySet.extra   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Peter Lithammer):

 * cc: Peter Lithammer (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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.e1f9ead144804367207c4233f317be6a%40djangoproject.com.


Re: [Django] #32518: Document that QuerySet.contains() should not be overused.

2022-01-25 Thread Django
#32518: Document that QuerySet.contains() should not be overused.
-+-
 Reporter:  Mariusz Felisiak |Owner:  John
 Type:   |  Hollingsworth
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  4.0
 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 John Hollingsworth):

 * owner:  (none) => John Hollingsworth
 * status:  new => assigned


Comment:

 I'll pick up this ticket where the previous PR left off

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

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


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

2022-01-25 Thread Django
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  raydeal
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by raydeal):

 Replying to [comment:49 Mariusz Felisiak]:
 Right, now I better understand what is expected solution. I am going to
 review again previous patch and change this one.

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

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


Re: [Django] #19527: Allow QuerySet.bulk_create() to set the primary key of its objects

2022-01-25 Thread Django
#19527: Allow QuerySet.bulk_create() to set the primary key of its objects
-+-
 Reporter:  Vlada Macek  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | Triage Stage:  Accepted
  QuerySet.bulk_create   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 It's also supported on SQLite 3.35+ (see
 93ed71e05802a47774b52503cdc3442686d686c1) and MariaDB 10.5+ (see
 98abc0c90e0eb7fe3a71cfa360962cf59605f1d3).

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

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


Re: [Django] #28519: Add filter(), exclude(), and other base QuerySet methods to combined QuerySets (union(), etc.)

2022-01-25 Thread Django
#28519: Add filter(), exclude(), and other base QuerySet methods to combined
QuerySets (union(), etc.)
-+-
 Reporter:  Stanislav Karpov |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  union,   | Triage Stage:  Accepted
  intersection, difference   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 I closed #30209 as a duplicate -- the case of trying to use `annotate()`
 after `union()`.

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

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


Re: [Django] #30209: Union with group by don't generate correct Subquery

2022-01-25 Thread Django
#30209: Union with group by don't generate correct Subquery
-+-
 Reporter:  Nikolas  |Owner:  Can
 |  Sarıgöl
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  union, group by  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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


Comment:

 A proper exception when calling `annotate()` after `union()`,
 `intersection()`, and `difference()` was added in
 1853383969a4c53bbeba998757c30410bd3df4bb.

 Closing as a duplicate of #28519.

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

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


Re: [Django] #20349: Don't load django.test when not testing

2022-01-25 Thread Django
#20349: Don't load django.test when not testing
--+
 Reporter:  Collin Anderson   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Testing framework |  Version:  dev
 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
--+

Comment (by Mariusz Felisiak ):

 In [changeset:"890bfa368c33d6ae19fe45cf1eed7e2e8d63160e" 890bfa36]:
 {{{
 #!CommitTicketReference repository=""
 revision="890bfa368c33d6ae19fe45cf1eed7e2e8d63160e"
 Refs #20349 -- Avoided loading testing libraries when not needed.
 }}}

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

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


Re: [Django] #30360: Support rotation of secret keys.

2022-01-25 Thread Django
#30360: Support rotation of secret keys.
---+-
 Reporter:  Andreas Pelme  |Owner:  tim-schilling
 Type:  New feature|   Status:  assigned
Component:  Core (Other)   |  Version:  dev
 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 Carlton Gibson):

 * owner:  Andreas Pelme => tim-schilling


Comment:

 [https://github.com/django/django/pull/15198 New PR] adding
 `SECRET_KEY_FALLBACKS` based on discussion/reviews of previous approaches.

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

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


Re: [Django] #30360: Support rotation of secret keys.

2022-01-25 Thread Django
#30360: Support rotation of secret keys.
---+-
 Reporter:  Andreas Pelme  |Owner:  Andreas Pelme
 Type:  New feature|   Status:  assigned
Component:  Core (Other)   |  Version:  dev
 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 Carlton Gibson):

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


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

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


Re: [Django] #33048: Documentation doesn't mention that using staticfiles' runserver doesn't use the middleware chain.

2022-01-25 Thread Django
#33048: Documentation doesn't mention that using staticfiles' runserver doesn't 
use
the middleware chain.
-+-
 Reporter:  Keryn Knight |Owner:
 Type:   |  valleyofblackpanther
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  dev
 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 Mariusz Felisiak):

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


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

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


Re: [Django] #33407: Radiolist etc. styling has changed since it's using div elements not ul elements

2022-01-25 Thread Django
#33407: Radiolist etc. styling has changed since it's using div elements not ul
elements
-+-
 Reporter:  Matthias Kestenholz  |Owner:  Carlton
 |  Gibson
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  4.0
 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 Carlton Gibson):

 * owner:  Mohamed Nabil Rady => Carlton Gibson
 * needs_better_patch:  1 => 0
 * needs_docs:  1 => 0


Comment:

 [https://github.com/django/django/pull/15333 Alternate PR]

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

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


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

2022-01-25 Thread Django
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  raydeal
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1


Comment:

 Replying to [comment:47 raydeal]:
 > I couldn't find correct rules because M2M worked as always, only changed
 behaviour of FK. When object is not saved it raises ValueError, when saved
 but related value is None returns , which is not consistent
 for me. Why?
 > Base on doubt from #17541
 https://code.djangoproject.com/ticket/17541#comment:8 I asked myself: What
 is the difference between not saved object with id (pk) refrerenced from
 other object and saved object with field containing None value referenced
 by other object, through FK both, from the relation point of view?
 > There is no difference - both of them have None value and making related
 query in both cases doesn't make sens.

 There is a huge difference for me. It's doesn't matter which field is
 pointed by m2m field, that's not crucial. The most important thing is that
 `Foo()` doesn't exist in the database so any related query makes no sense,
 and IMO we should raise an exception only in this particular case. You can
 start a discussion on DevelopersMailingList if you don't agree, where
 you'll reach a wider audience and see what other think.

 Moreover proposed change is not a part of the ticket description, it's
 backward incompatible, and was not accepted per se.

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

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