Re: [Django] #34395: Update admin's jQuery to 3.6.4.

2023-03-08 Thread Django 
#34395: Update admin's jQuery to 3.6.4.
-+-
 Reporter:  Mariusz Felisiak |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  4.2
 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 Mariusz Felisiak ):

 In [changeset:"87a55e0b51771d42bb90087bd9805db983f48fd7" 87a55e0]:
 {{{
 #!CommitTicketReference repository=""
 revision="87a55e0b51771d42bb90087bd9805db983f48fd7"
 [4.2.x] Fixed #34395 -- Updated admin's jQuery to 3.6.4.

 Backport of 18473004afd82a616ba6c9ac22f476347fde4846 from main
 }}}

-- 
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/01070186c55ea59b-4a11d05b-c1cb-4369-b394-3b2b66420c0d-00%40eu-central-1.amazonses.com.

Re: [Django] #34395: Update admin's jQuery to 3.6.4.

2023-03-08 Thread Django 
#34395: Update admin's jQuery to 3.6.4.
-+-
 Reporter:  Mariusz Felisiak |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  4.2
 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 GitHub ):

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


Comment:

 In [changeset:"18473004afd82a616ba6c9ac22f476347fde4846" 18473004]:
 {{{
 #!CommitTicketReference repository=""
 revision="18473004afd82a616ba6c9ac22f476347fde4846"
 Fixed #34395 -- Updated admin's jQuery to 3.6.4.
 }}}

-- 
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/01070186c55e1b27-125a394e-5ed7-495d-a124-4d7b827e667f-00%40eu-central-1.amazonses.com.

[Django] #34396: Add Postgres+Windows to CI

2023-03-08 Thread Django 
#34396: Add Postgres+Windows to CI
-+
   Reporter:  David Smith|  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Uncategorized  |Version:  4.1
   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  |
-+
 Following #34381 I wonder if it's worth adding a postgres+windows workflow
 to the GitHub action workflows? Maybe run it once a day/week rather than
 on every PR/commit?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070186c55ab88f-9ef7753e-c8ac-4d62-b2f8-4436a409cf80-00%40eu-central-1.amazonses.com.

Re: [Django] #34395: Update admin's jQuery to 3.6.4.

2023-03-08 Thread Django 
#34395: Update admin's jQuery to 3.6.4.
-+-
 Reporter:  Mariusz Felisiak |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  4.2
 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 Carlton Gibson):

 * 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/01070186c544bc14-02a6a8db-82ca-4a20-ad63-165f03b68946-00%40eu-central-1.amazonses.com.

Re: [Django] #34388: Added support for direct usage of Choices classes on model fields

2023-03-08 Thread Django 
#34388: Added support for direct usage of Choices classes on model fields
-+-
 Reporter:  T. Franzel   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

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


Comment:

 > Passing a Choices class makes sense, instead of doing the strange
 choices=MyChoices.choices manipulation

 I think that's right — it would feel nice.

 But we're not going to remove the support for lists of pairs...
 (If we loosen here then typing for choices goes from list of pairs to list
 of pair OR Choices subclass, which I can imagine folk complaining about.)


 Then there's the separate point about storing a reference that we're not
 going to use.


 Let's close then. 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070186c542200d-2f3d6b44-9a2c-41bc-b2e3-3005d36d2493-00%40eu-central-1.amazonses.com.

Re: [Django] #34395: Update admin's jQuery to 3.6.4.

2023-03-08 Thread Django 
#34395: Update admin's jQuery to 3.6.4.
-+-
 Reporter:  Mariusz Felisiak |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  4.2
 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 Mariusz Felisiak):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/16639 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/01070186c5420eb9-08f23008-76af-41a5-b37d-7c8279624a0b-00%40eu-central-1.amazonses.com.

Re: [Django] #34395: Update admin's jQuery to 3.6.4.

2023-03-08 Thread Django 
#34395: Update admin's jQuery to 3.6.4.
-+-
 Reporter:  Mariusz Felisiak |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  4.2
 Severity:  Release blocker  |   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 Claude Paroz):

 * stage:  Unreviewed => Accepted


Comment:

 Now is the time :-)

-- 
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/01070186c53ca574-88b69ab1-c872-4c2e-af19-31d30371e7ad-00%40eu-central-1.amazonses.com.

[Django] #34395: Update admin's jQuery to 3.6.4.

2023-03-08 Thread Django 
#34395: Update admin's jQuery to 3.6.4.
-+-
   Reporter:  Mariusz|  Owner:  Mariusz Felisiak
  Felisiak   |
   Type:  Bug| Status:  assigned
  Component: |Version:  4.2
  contrib.admin  |
   Severity:  Release|   Keywords:
  blocker|
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 We updated admin's jQuery to 3.6.3 in
 5cf9ff970e08b10d3f7d62734dbce9e8eaeff453. Unfortunately, it introduced a
 regression in selectors that are strictly invalid but worked in jQuery <
 3.6.3. Since Django 4.2 is still in beta I'd recommend updating admin's
 jQuery to 3.6.4 in Django 4.2.

 See ​3.6.4 [https://blog.jquery.com/2023/03/08/jquery-3-6-4-released-
 selector-forgiveness/ release note].

-- 
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/01070186c4e75574-a77ea302-1d52-4d81-8a52-944a49d34564-00%40eu-central-1.amazonses.com.

Re: [Django] #34394: ASGIRequest doesn't respect settings.FORCE_SCRIPT_NAME. (was: django.core.handlers.asgi.ASGIRequest.script_name not work with settings.FORCE_SCRIPT_NAME)

2023-03-08 Thread Django 
#34394: ASGIRequest doesn't respect settings.FORCE_SCRIPT_NAME.
--+
 Reporter:  julyzergcn|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  HTTP handling |  Version:  4.1
 Severity:  Normal|   Resolution:
 Keywords:  asgi SCRIPT_NAME  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Mariusz Felisiak):

 * cc: Carlton Gibson, Andrew Godwin (added)
 * component:  Core (URLs) => HTTP handling
 * stage:  Unreviewed => Accepted


Comment:

 Thanks for the report. It seems that `ASGIRequest` should take
 `FORCE_SCRIPT_NAME` into account (as `WSGIRequest`), e.g.
 {{{#!diff
 diff --git a/django/core/handlers/asgi.py b/django/core/handlers/asgi.py
 index 569157b277..c5eb87c712 100644
 --- a/django/core/handlers/asgi.py
 +++ b/django/core/handlers/asgi.py
 @@ -40,7 +40,7 @@ class ASGIRequest(HttpRequest):
  self._post_parse_error = False
  self._read_started = False
  self.resolver_match = None
 -self.script_name = self.scope.get("root_path", "")
 +self.script_name = get_script_prefix(scope)
  if self.script_name:
  # TODO: Better is-prefix checking, slash handling?
  self.path_info = scope["path"].removeprefix(self.script_name)
 @@ -169,7 +169,7 @@ class ASGIHandler(base.BaseHandler):
  except RequestAborted:
  return
  # Request is complete and can be served.
 -set_script_prefix(self.get_script_prefix(scope))
 +set_script_prefix(get_script_prefix(scope))
  await signals.request_started.asend(sender=self.__class__,
 scope=scope)
  # Get the request and check for basic issues.
  request, error_response = self.create_request(scope, body_file)
 @@ -310,10 +310,11 @@ class ASGIHandler(base.BaseHandler):
  )
  position += cls.chunk_size

 -def get_script_prefix(self, scope):
 -"""
 -Return the script prefix to use from either the scope or a
 setting.
 -"""
 -if settings.FORCE_SCRIPT_NAME:
 -return settings.FORCE_SCRIPT_NAME
 -return scope.get("root_path", "") or ""
 +
 +def get_script_prefix(scope):
 +"""
 +Return the script prefix to use from either the scope or a setting.
 +"""
 +if settings.FORCE_SCRIPT_NAME:
 +return settings.FORCE_SCRIPT_NAME
 +return scope.get("root_path", "") or ""
 }}}

 Would you like to prepare a patch via GitHub PR? (a regression test is
 required.)

-- 
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/01070186c4d809b9-0968fd87-7329-49d2-9acd-70bd8df22705-00%40eu-central-1.amazonses.com.

Re: [Django] #34393: A filter query returns more items than the original queryset provides after applying INNER JOIN

2023-03-08 Thread Django 
#34393: A filter query returns more items than the original queryset provides 
after
applying INNER JOIN
-+-
 Reporter:  Ľuboš Mjachky|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  filter query | Triage Stage:
  duplicate distinct |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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


Comment:

 This is a [https://docs.djangoproject.com/en/stable/topics/db/queries
 /#spanning-multi-valued-relationships documented] behavior. You can use
 `Subquery()` to prevent duplicates.

-- 
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/01070186c4c453cd-d1dbfb5e-f765-4db9-b999-e1b34309a499-00%40eu-central-1.amazonses.com.

[Django] #34394: django.core.handlers.asgi.ASGIRequest.script_name not work with settings.FORCE_SCRIPT_NAME

2023-03-08 Thread Django 
#34394: django.core.handlers.asgi.ASGIRequest.script_name not work with
settings.FORCE_SCRIPT_NAME
---+--
   Reporter:  julyzergcn   |  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  Core (URLs)  |Version:  4.1
   Severity:  Normal   |   Keywords:  asgi SCRIPT_NAME
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+--
 For example, I have settings.FORCE_SCRIPT_NAME = '/some-prefix'
 I start a django server with command: daphne
 django_project.asgi:application
 And I navigate to the http://localhost:8000/admin/login, and see the login
 form action url is "/admin/login" which is wrong, which should be "/some-
 prefix/admin/login"

-- 
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/01070186c46c51df-ca7b1e66-ef1d-45a2-8363-7c388e66efad-00%40eu-central-1.amazonses.com.

Re: [Django] #15727: Add support for Content-Security-Policy (CSP) to core

2023-03-08 Thread Django 
#15727: Add support for Content-Security-Policy (CSP) to core
---+-
 Reporter:  db.pub.mail@…  |Owner:  Anvesh Mishra
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  Version:  dev
 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 Petr Přikryl):

 * cc: Petr Přikryl (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/01070186c37da2e8-6895807b-6da0-43e5-a3ca-a45092bc07aa-00%40eu-central-1.amazonses.com.

[Django] #34393: A filter query returns more items than the original queryset provides after applying INNER JOIN

2023-03-08 Thread Django 
#34393: A filter query returns more items than the original queryset provides 
after
applying INNER JOIN
-+-
   Reporter:  Ľuboš  |  Owner:  nobody
  Mjachky|
   Type: | Status:  new
  Uncategorized  |
  Component:  Database   |Version:  3.2
  layer (models, ORM)|   Keywords:  filter query
   Severity:  Normal |  duplicate distinct
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 In our project, we identified that the filter query returns more entries
 than the number of entries stored in the initial queryset.

 The following piece of code is involved:
 {{{
 # qs.count() == 4
 scoped_repos = repo_viewset.get_queryset().values_list("pk", flat=True)
 filtered_content = qs.filter(repositories__in=scoped_repos)
 # filtered_content.count() == 8
 }}}

 The generated query:
 {{{
 SELECT * FROM "rpm_package" INNER JOIN "core_content" ON
 ("rpm_package"."content_ptr_id" = "core_content"."pulp_id")
 INNER JOIN "core_repositorycontent" ON ("core_content"."pulp_id" =
 "core_repositorycontent"."content_id")
 WHERE "core_repositorycontent"."repository_id" IN (c35b7039-2c2c-48e3
 -8f4f-b0eeabad8af1, ee39a78b-9dd5-4bdf-85d9-eb6406b6ef49)
 }}}

 One of the things being noticed is that the query is constructed with an
 INNER JOIN clause instead of a LEFT JOIN clause. The
 core_repositorycontent table contains a lot of duplicates. We believe that
 this should not be a problem. Adding the distinct() query at the end of
 the call resolves the issue. See
 https://github.com/pulp/pulpcore/pull/3642.

 The question is whether this is a bug in Django (i.e., a filter query can
 return more elements than there are in the original queryset) or on our
 side, and we should restructure the query in a specific way. Any advice is
 welcome.

-- 
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/01070186c2cec158-38982f63-7580-4ee8-99ee-fc2ebf8e9136-00%40eu-central-1.amazonses.com.

Re: [Django] #34380: Make URLField assume "https".

2023-03-08 Thread Django 
#34380: Make URLField assume "https".
-+-
 Reporter:  Coen van der Kamp|Owner:  Coen van
 Type:   |  der Kamp
  Cleanup/optimization   |   Status:  assigned
Component:  Forms|  Version:  4.1
 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
-+-

Comment (by Coen van der Kamp):

 I've updated the PR (improved the patch).
 https://github.com/django/django/pull/16614/files
 Not sure if I need to update something on this ticket.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070186c2b5ef5b-ae6ee3b5-05cf-4fb1-82c4-b7eda75e7c54-00%40eu-central-1.amazonses.com.

Re: [Django] #16055: Filtering over generic relations with TextField/CharField object_id breaks in postgres

2023-03-08 Thread Django 
#16055: Filtering over generic relations with TextField/CharField object_id 
breaks
in postgres
-+-
 Reporter:  anonymous|Owner:  David
 |  Wobrock
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  3.2
  contrib.contenttypes   |
 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 David Wobrock):

 * needs_better_patch:  1 => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070186c21754d7-5d0323cd-5d54-40a4-beeb-35e73bd5102c-00%40eu-central-1.amazonses.com.

Re: [Django] #27397: Querying with an integer larger than SQLite supports crashes with OverflowError

2023-03-08 Thread Django 
#27397: Querying with an integer larger than SQLite supports crashes with
OverflowError
-+-
 Reporter:  Ramin Farajpour  |Owner:  Simon
  Cami   |  Charette
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  SQLite, Error| Triage Stage:  Accepted
  Handling   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * needs_better_patch:  1 => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070186c2044745-bc3bf665-bb2c-484d-8934-696e7e1abf78-00%40eu-central-1.amazonses.com.

Re: [Django] #27397: Querying with an integer larger than SQLite supports crashes with OverflowError

2023-03-08 Thread Django 
#27397: Querying with an integer larger than SQLite supports crashes with
OverflowError
-+-
 Reporter:  Ramin Farajpour  |Owner:  Simon
  Cami   |  Charette
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  SQLite, Error| Triage Stage:  Accepted
  Handling   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070186c123dcda-938b5cd0-2a5f-41e9-956a-6ebfecaef0e5-00%40eu-central-1.amazonses.com.

Re: [Django] #34370: IntegerField validators don't work if the database is SQLite, leading to overflow errors

2023-03-08 Thread Django 
#34370: IntegerField validators don't work if the database is SQLite, leading to
overflow errors
-+-
 Reporter:  Alex Urbanowicz  |Owner:  Mohamed
 Type:   |  Nabil Rady
  Cleanup/optimization   |   Status:  closed
Component:  Database layer   |  Version:  4.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  IntegerField SQLite  | Triage Stage:  Ready for
  MaxValueValidator  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"32d4b61c313be5169137047e9fb3668da20a5d89" 32d4b61c]:
 {{{
 #!CommitTicketReference repository=""
 revision="32d4b61c313be5169137047e9fb3668da20a5d89"
 Fixed #34370 -- Added integer fields validation as 64-bit 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070186c1184fd7-daba7d38-aee4-421e-9208-70fc368bb21e-00%40eu-central-1.amazonses.com.

Re: [Django] #34370: IntegerField validators don't work if the database is SQLite, leading to overflow errors

2023-03-08 Thread Django 
#34370: IntegerField validators don't work if the database is SQLite, leading to
overflow errors
-+-
 Reporter:  Alex Urbanowicz  |Owner:  Mohamed
 Type:   |  Nabil Rady
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  4.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  IntegerField SQLite  | Triage Stage:  Ready for
  MaxValueValidator  |  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_docs:  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/01070186c0f95021-079db9a7-45ce-4393-b8fe-ece0403a98ce-00%40eu-central-1.amazonses.com.

Re: [Django] #34392: Allow using test client response.json() with StreamingHttpResponse

2023-03-08 Thread Django 
#34392: Allow using test client response.json() with StreamingHttpResponse
---+--
 Reporter:  vainu-arto |Owner:  vainu-arto
 Type:  New feature|   Status:  assigned
Component:  Testing framework  |  Version:  dev
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Carlton Gibson):

 * needs_tests:  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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070186c0e973e3-1904a203-bf4c-4973-a9c9-88860f2dc356-00%40eu-central-1.amazonses.com.

Re: [Django] #34392: Allow using test client response.json() with StreamingHttpResponse

2023-03-08 Thread Django 
#34392: Allow using test client response.json() with StreamingHttpResponse
---+--
 Reporter:  vainu-arto |Owner:  vainu-arto
 Type:  New feature|   Status:  assigned
Component:  Testing framework  |  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):

 * stage:  Unreviewed => Accepted


Comment:

 OK, I think this is likely an ok addition.

 `getvalue()` should allow for an async iterator if we're going to use it
 this way. (Consuming `self` rather than `self.streaming_content` would be
 one way, but the warning would need to be caught.)

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070186c0e8a2bb-21b6dc70-63ac-4050-8411-0bde03e149ec-00%40eu-central-1.amazonses.com.

Re: [Django] #30686: Improve utils.text.Truncator &co to use a full HTML parser.

2023-03-08 Thread Django 
#30686: Improve utils.text.Truncator &co to use a full HTML parser.
---+---
 Reporter:  Thomas Hooper  |Owner:  David Smith
 Type:  Bug|   Status:  assigned
Component:  Utilities  |  Version:  dev
 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 Carlton Gibson):

 * needs_better_patch:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070186c0db83fb-0bab7743-805f-40f6-9c60-e2b8c052f9c2-00%40eu-central-1.amazonses.com.

Re: [Django] #34384: SECRET_KEY_FALLBACKS is not used for sessions

2023-03-08 Thread Django 
#34384: SECRET_KEY_FALLBACKS is not used for sessions
-+-
 Reporter:  Eric Zarowny |Owner:  David
 |  Wobrock
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  4.1
 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 Mariusz Felisiak ):

 In [changeset:"ba1654cb54eccef3ba29e455cd5065aed84e1f90" ba1654cb]:
 {{{
 #!CommitTicketReference repository=""
 revision="ba1654cb54eccef3ba29e455cd5065aed84e1f90"
 [4.1.x] Fixed #34384 -- Fixed session validation when rotation secret
 keys.

 Bug in 0dcd549bbe36c060f536ec270d34d9e7d4b8e6c7.

 Thanks Eric Zarowny for the report.

 Backport of 2396933ca99c6bfb53bda9e53968760316646e01 from main
 }}}

-- 
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/01070186c0c91441-1e66cca7-49e2-4938-b159-6602d3b7e3db-00%40eu-central-1.amazonses.com.

Re: [Django] #34384: SECRET_KEY_FALLBACKS is not used for sessions

2023-03-08 Thread Django 
#34384: SECRET_KEY_FALLBACKS is not used for sessions
-+-
 Reporter:  Eric Zarowny |Owner:  David
 |  Wobrock
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  4.1
 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 Mariusz Felisiak ):

 In [changeset:"6937c921691746a85e2993406b46da0527b6f2ee" 6937c921]:
 {{{
 #!CommitTicketReference repository=""
 revision="6937c921691746a85e2993406b46da0527b6f2ee"
 [4.2.x] Fixed #34384 -- Fixed session validation when rotation secret
 keys.

 Bug in 0dcd549bbe36c060f536ec270d34d9e7d4b8e6c7.

 Thanks Eric Zarowny for the report.

 Backport of 2396933ca99c6bfb53bda9e53968760316646e01 from main
 }}}

-- 
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/01070186c0c8c7a7-fcef4e5e-2e05-4949-839e-470f57adf6c8-00%40eu-central-1.amazonses.com.

Re: [Django] #34384: SECRET_KEY_FALLBACKS is not used for sessions

2023-03-08 Thread Django 
#34384: SECRET_KEY_FALLBACKS is not used for sessions
-+-
 Reporter:  Eric Zarowny |Owner:  David
 |  Wobrock
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  4.1
 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 Mariusz Felisiak ):

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


Comment:

 In [changeset:"2396933ca99c6bfb53bda9e53968760316646e01" 2396933c]:
 {{{
 #!CommitTicketReference repository=""
 revision="2396933ca99c6bfb53bda9e53968760316646e01"
 Fixed #34384 -- Fixed session validation when rotation secret keys.

 Bug in 0dcd549bbe36c060f536ec270d34d9e7d4b8e6c7.

 Thanks Eric Zarowny for the report.
 }}}

-- 
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/01070186c0c806e3-ed92b0fe-08cc-42a3-9ce8-fcf49b7396b0-00%40eu-central-1.amazonses.com.

Re: [Django] #34392: Allow using test client response.json() with StreamingHttpResponse

2023-03-08 Thread Django 
#34392: Allow using test client response.json() with StreamingHttpResponse
---+--
 Reporter:  vainu-arto |Owner:  vainu-arto
 Type:  New feature|   Status:  assigned
Component:  Testing framework  |  Version:  dev
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by vainu-arto):

 * owner:  nobody => vainu-arto
 * status:  new => assigned


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070186c0b8fb0f-65c019f9-0a51-4dbe-bd12-a875330e59b6-00%40eu-central-1.amazonses.com.

[Django] #34392: Allow using test client response.json() with StreamingHttpResponse

2023-03-08 Thread Django 
#34392: Allow using test client response.json() with StreamingHttpResponse
-+
   Reporter:  vainu-arto |  Owner:  nobody
   Type:  New feature| Status:  new
  Component:  Testing framework  |Version:  dev
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 This doesn't work since the ClientMixin._parse_json() method uses
 response.content directly instead of using the response.getvalue() wrapper
 which abstracts away the difference between the Response implementations.

-- 
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/01070186c0b85464-41285db8-9bbc-454f-87fe-d599b5e66804-00%40eu-central-1.amazonses.com.

Re: [Django] #34322: ManifestStaticFilesStorage crashes on commented JavaScript import statements

2023-03-08 Thread Django 
#34322: ManifestStaticFilesStorage crashes on commented JavaScript import
statements
-+-
 Reporter:  Adam Johnson |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.staticfiles  |  Version:  4.2
 Severity:  Normal   |   Resolution:  duplicate
 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):

 Adam, is your current patch shareable?

 If the current state is not acceptable for 4.2, we could still make that
 feature togglable with an opt-in/opt-out flag on the class as I suggested
 on comment:8.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070186c0a17aaf-f35de16b-1aaa-4b8c-b2f6-1dd34d895444-00%40eu-central-1.amazonses.com.

Re: [Django] #34391: Add async interface to contrib.auth

2023-03-08 Thread Django 
#34391: Add async interface to contrib.auth
--+--
 Reporter:  Jon Janzen|Owner:  Jon Janzen
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:  async | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by Carlton Gibson):

 * needs_docs:  0 => 1
 * needs_tests:  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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070186c08c89d9-f7df9119-87ab-4b60-ada8-cbf03d5ada7c-00%40eu-central-1.amazonses.com.

Re: [Django] #34384: SECRET_KEY_FALLBACKS is not used for sessions

2023-03-08 Thread Django 
#34384: SECRET_KEY_FALLBACKS is not used for sessions
-+-
 Reporter:  Eric Zarowny |Owner:  David
 |  Wobrock
 Type:  Bug  |   Status:  assigned
Component:  contrib.auth |  Version:  4.1
 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):

 * 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/01070186c07a1f61-fce406b8-3cd7-4ab2-b739-5be7bc707d3a-00%40eu-central-1.amazonses.com.

Re: [Django] #32172: Adapt signals to allow async handlers

2023-03-08 Thread Django 
#32172: Adapt signals to allow async handlers
-+-
 Reporter:  Carlton Gibson   |Owner:  Jon
 |  Janzen
 Type:  New feature  |   Status:  closed
Component:  Core (Other) |  Version:  dev
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  async| 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 GitHub ):

 In [changeset:"9b224579875e30203d079cc2fee83b116d98eb78" 9b224579]:
 {{{
 #!CommitTicketReference repository=""
 revision="9b224579875e30203d079cc2fee83b116d98eb78"
 Refs #32172 -- Used asgiref coroutine shim in async signals tests.

 Bug in e83a88566a71a2353cebc35992c110be0f8628af.
 }}}

-- 
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/01070186c06d0f6c-ce2b9731-a6c7-4b71-abad-f4e35e6719d3-00%40eu-central-1.amazonses.com.

Re: [Django] #33817: Use python-oracledb instead of cx-oracle

2023-03-08 Thread Django 
#33817: Use python-oracledb instead of cx-oracle
-+-
 Reporter:  Alexander Shishenko  |Owner:  Jingbei
 |  Li
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jingbei Li):

 * needs_better_patch:  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/01070186c050da05-52f23ebb-a3fc-4014-b992-51cab50ee659-00%40eu-central-1.amazonses.com.