Re: [Django] #33552: has_key, has_keys, and has_any_keys JSONField() lookups don't handle numeric keys on SQLite, MySQL, and Oracle.

[Django]

#33552: has_key, has_keys, and has_any_keys JSONField() lookups don't handle
numeric keys on SQLite, MySQL, and Oracle.
-+-
 Reporter:  TheTerrasque |Owner:  Sage
 |  Abdullah
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.0
  (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
-+-
Changes (by Sage Abdullah):

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


Comment:

 [https://github.com/django/django/pull/15503 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/0107017f7ccd553c-678cda2e-40cf-4e03-b1d2-fba810ba912c-00%40eu-central-1.amazonses.com.

Re: [Django] #33571: Fix handling empty string for If-Modified-Since header

[Django]

#33571: Fix handling empty string for If-Modified-Since header
-+-
 Reporter:  Collin Anderson  |Owner:  Collin
 |  Anderson
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  Version:  4.0
 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 Collin Anderson):

 Could it maybe be considered a "Crashing bug", because it crashes rather
 than ignores a bad value? If not that's fine. I suppose most people follow
 the advice in the docs and don't use `django.views.static.serve()` in
 production. :)

-- 
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/0107017f7aa24ed1-8736e2e7-60c9-4123-8334-07916b25d47c-00%40eu-central-1.amazonses.com.

Re: [Django] #33571: Fix handling empty string for If-Modified-Since header

[Django]

#33571: Fix handling empty string for If-Modified-Since header
-+-
 Reporter:  Collin Anderson  |Owner:  Collin
 |  Anderson
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  Version:  4.0
 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):

 Replying to [comment:4 Collin Anderson]:
 > I guess this has been broken since 3.1. Any chance this could be
 backported? At least to 4.0? (Feel free to leave in catching
 `AssertionError`) I suppose it would need a release note too.

 This is a regression in Django 3.1 which is not supported anymore. Per our
 backporting policy this means it doesn't qualify for a backport to 4.0.x
 or 3.2.x anymore. See [https://docs.djangoproject.com/en/stable/internals
 /release-process/ Django’s release process] for more details.

-- 
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/0107017f7a926369-89a9605d-7943-4314-b1e4-e6d7b39287c5-00%40eu-central-1.amazonses.com.

[Django] #33573: Add native async support to redis cache backend

[Django]

#33573: Add native async support to redis cache backend
---+
   Reporter:  AngellusMortis   |  Owner:  nobody
   Type:  New feature  | Status:  new
  Component:  Core (Cache system)  |Version:  dev
   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|
---+
 The latest version of redis-py will support both sync and async clients so
 `sync_to_async` will no longer be necessary so it would be nice if the out
 of the box Redis cache backend supports both natively as well.

 https://github.com/redis/redis-py/releases/tag/v4.2.0rc1

 It may be a bit premature since 4.2.0 is still RC, but I wanted to get a
 ticket out there so it can be on someones radar.

-- 
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/0107017f79e0faf6-d34fbaf5-5ba6-4074-a358-797bea3bfd60-00%40eu-central-1.amazonses.com.

Re: [Django] #33571: Fix handling empty string for If-Modified-Since header

[Django]

#33571: Fix handling empty string for If-Modified-Since header
-+-
 Reporter:  Collin Anderson  |Owner:  Collin
 |  Anderson
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  Version:  4.0
 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 Collin Anderson):

 I guess this has been broken since 3.1. Any chance this could be
 backported? At least to 4.0? (Feel free to leave in catching
 `AssertionError`) I suppose it would need a release note too.

-- 
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/0107017f790e7092-b2e2dd6f-e9cc-49ff-a924-27c1fa4ad715-00%40eu-central-1.amazonses.com.

Re: [Django] #26401: Allow auth machinery to be used without installing auth app

[Django]

#26401: Allow auth machinery to be used without installing auth app
--+
 Reporter:  Matt Johnson  |Owner:  (none)
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  auth  | 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):

 * status:  assigned => new


-- 
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/0107017f78da88a0-3f49e916-4964-4839-8236-c9deba9645c9-00%40eu-central-1.amazonses.com.

Re: [Django] #26401: Allow auth machinery to be used without installing auth app

[Django]

#26401: Allow auth machinery to be used without installing auth app
--+
 Reporter:  Matt Johnson  |Owner:  (none)
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  auth  | 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):

 * owner:  Andrew Konoff => (none)
 * 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/0107017f78da6e6b-4c9c940f-ea8e-4799-9bf6-0c5bd0687bd8-00%40eu-central-1.amazonses.com.

Re: [Django] #2137: Add drag and drop ordering for inlines to set order_with_respect_to in admin interface

[Django]

#2137: Add drag and drop ordering for inlines to set order_with_respect_to in
admin interface
---+
 Reporter:  anonymous  |Owner:  (none)
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:
 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 Mariusz Felisiak):

 * status:  assigned => new


-- 
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/0107017f78d833a0-da187386-0246-4e21-a26a-ad8ba333c0dd-00%40eu-central-1.amazonses.com.

Re: [Django] #2137: Add drag and drop ordering for inlines to set order_with_respect_to in admin interface

[Django]

#2137: Add drag and drop ordering for inlines to set order_with_respect_to in
admin interface
---+
 Reporter:  anonymous  |Owner:  (none)
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:
 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 Mariusz Felisiak):

 * owner:  xian => (none)
 * 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/0107017f78d82020-8c835ee5-2500-4cd9-9845-c7a54e17f577-00%40eu-central-1.amazonses.com.

Re: [Django] #22078: views.Feed methods cannot be decorated

[Django]

#22078: views.Feed methods cannot be decorated
-+
 Reporter:  Germano Gabbianelli  |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  contrib.syndication  |  Version:  1.6
 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 Mariusz Felisiak):

 * owner:  coldmin => (none)
 * status:  assigned => new


-- 
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/0107017f787d542d-b667234a-375c-448e-9b1c-38524fab65cf-00%40eu-central-1.amazonses.com.

Re: [Django] #19221: Check that cache keys are string

[Django]

#19221: Check that cache keys are string
-+
 Reporter:  Mark Hughes  |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Core (Cache system)  |  Version:  dev
 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 Mariusz Felisiak):

 * owner:  Dan Stephenson => (none)
 * status:  assigned => new


-- 
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/0107017f78741a5f-5e377152-1028-428d-9be1-d99d73cf364b-00%40eu-central-1.amazonses.com.

Re: [Django] #15099: ModelFormset.queryset requirement is too strict

[Django]

#15099: ModelFormset.queryset requirement is too strict
---+
 Reporter:  Jari Pennanen  |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Forms  |  Version:  1.2
 Severity:  Normal |   Resolution:  wontfix
 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 Mariusz Felisiak):

 * status:  new => closed
 * type:  Bug => New feature
 * resolution:   => wontfix


Comment:

 This is really niche and probably it's not worth additional complexity. We
 can reconsider this decision only if someone provides PoC.

-- 
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/0107017f786baa8d-c1d97ed9-5856-4bb6-8e0c-0715d37b4c81-00%40eu-central-1.amazonses.com.

Re: [Django] #28897: QuerySet.update() raises FieldError on queryset ordered by an annotated field.

[Django]

#28897: QuerySet.update() raises FieldError on queryset ordered by an annotated
field.
-+-
 Reporter:  Colton Hicks |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Admin Interface, | Triage Stage:  Accepted
  Custom Action, Annotated Field,|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 Saeed, Have you seen my
 [https://code.djangoproject.com/ticket/28897#comment:6 comment]?

-- 
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/0107017f783978b1-92d928ee-6d10-47cb-924a-01e82634b4d3-00%40eu-central-1.amazonses.com.