Re: [Django] #34428: ASGIStaticFilesHandler raises warning.

[Django]

#34428: ASGIStaticFilesHandler raises warning.
-+-
 Reporter:  Carlton Gibson   |Owner:  Carlton
 |  Gibson
 Type:  Bug  |   Status:  closed
Component:  contrib.staticfiles  |  Version:  4.2
 Severity:  Release blocker  |   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:"ae824eceb1ddcaef336677bf9a6e704097cd2309" ae824ece]:
 {{{
 #!CommitTicketReference repository=""
 revision="ae824eceb1ddcaef336677bf9a6e704097cd2309"
 [4.2.x] Fixed #34428 -- Made ASGIStaticFilesHandler adapt response to
 async iterator.

 Bug in 0bd2c0c9015b53c41394a1c0989afbfd94dc2830.
 Backport of 02c356f2f3945b8075735d485c3cf48cad991011 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/0107018705bbccdd-fdc0e7f0-789b-4dad-807c-f09a812430d0-00%40eu-central-1.amazonses.com.

Re: [Django] #34428: ASGIStaticFilesHandler raises warning.

[Django]

#34428: ASGIStaticFilesHandler raises warning.
-+-
 Reporter:  Carlton Gibson   |Owner:  Carlton
 |  Gibson
 Type:  Bug  |   Status:  closed
Component:  contrib.staticfiles  |  Version:  4.2
 Severity:  Release blocker  |   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 GitHub ):

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


Comment:

 In [changeset:"02c356f2f3945b8075735d485c3cf48cad991011" 02c356f]:
 {{{
 #!CommitTicketReference repository=""
 revision="02c356f2f3945b8075735d485c3cf48cad991011"
 Fixed #34428 -- Made ASGIStaticFilesHandler adapt response to async
 iterator.

 Bug in 0bd2c0c9015b53c41394a1c0989afbfd94dc2830.
 }}}

-- 
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/0107018705ba8885-83614b00-d953-4f1a-a7c8-6fb8d1732aba-00%40eu-central-1.amazonses.com.

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

[Django]

#34388: Added support for direct usage of Choices classes on model fields
-+-
 Reporter:  T. Franzel   |Owner:  T.
 |  Franzel
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  dev
  (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 Mariusz Felisiak ):

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


Comment:

 In [changeset:"a2eaea8f22305b57dff3ab13add2e2887287bb6f" a2eaea8]:
 {{{
 #!CommitTicketReference repository=""
 revision="a2eaea8f22305b57dff3ab13add2e2887287bb6f"
 Fixed #34388 -- Allowed using choice enumeration types directly on model
 and form fields.
 }}}

-- 
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/0107018705a9f580-f499bd04-e160-4d6c-8fd9-b600a746bb4b-00%40eu-central-1.amazonses.com.

Re: [Django] #34430: Custom exception handler not called

[Django]

#34430: Custom exception handler not called
-+--
 Reporter:  frontierconnect  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Generic views|  Version:  4.1
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by Mariusz Felisiak):

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


Comment:

 There is no such setting in Django as `REST_FRAMEWORK`.

 Please don't use Trac as a support channel. Closing per
 TicketClosingReasons/UseSupportChannels.

-- 
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/0107018705a79f1c-0a351aeb-dcc6-4a9b-8b69-f48282268def-00%40eu-central-1.amazonses.com.

[Django] #34430: Custom exception handler not called

[Django]

#34430: Custom exception handler not called
---+
   Reporter:  frontierconnect  |  Owner:  nobody
   Type:  Uncategorized| Status:  new
  Component:  Generic views|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|
---+
 coded my own method custom_exception_handler for exception handling but
 for authentication exception this callback is not called

 I configured in my settings the callback under:

 REST_FRAMEWORK = {'EXCEPTION_HANDLER' :
 'myapp.api.response.custom_exception_handler',}

 Simple performing a api call without token (that requires auth), it is
 raised NotAuthenticated exception, that is returning on Response

 {"detail":"Authentication credentials were not provided."}

 My view class is inherited from rest_framework.viewsets.GenericViewSet
 that inherits APIView

 I noticed that the exception handler callback is managed in APIView

 exception_handler = self.get_exception_handler()

 that returns settings.EXCEPTION_HANDLER that pointing to default
 rest_framework exception handler.

 Seems that REST_FRAMEWORK configuration is not taken into account.

-- 
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/010701870597c934-6b9bfc66-c826-4829-a64f-cc6b2c9f84ff-00%40eu-central-1.amazonses.com.

Re: [Django] #34428: ASGIStaticFilesHandler raises warning.

[Django]

#34428: ASGIStaticFilesHandler raises warning.
-+-
 Reporter:  Carlton Gibson   |Owner:  Carlton
 |  Gibson
 Type:  Bug  |   Status:  assigned
Component:  contrib.staticfiles  |  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):

 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/010701870572d57d-08b817d5-0170-48ec-a94e-d3678b5cab9f-00%40eu-central-1.amazonses.com.

Re: [Django] #34427: Improve error message for incorrect context processors

[Django]

#34427: Improve error message for incorrect context processors
-+
 Reporter:  Adam Johnson |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Template 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 Claude Paroz):

 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018705224aea-cad8f6e6-73d2-40e6-b008-59cf93867d91-00%40eu-central-1.amazonses.com.

Re: [Django] #34428: ASGIStaticFilesHandler raises warning.

[Django]

#34428: ASGIStaticFilesHandler raises warning.
-+-
 Reporter:  Carlton Gibson   |Owner:  Carlton
 |  Gibson
 Type:  Bug  |   Status:  assigned
Component:  contrib.staticfiles  |  Version:  4.2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by Carlton Gibson:

Old description:

> #33735 added async support to `StreamingHttpResponse` for Django 4.2.
>
> With Django 4.2rc1 and Daphne, `StreamingHttpResponse` raises a warning
> about the incorrect iterator type being used:
>
> > http/response.py:534: Warning: StreamingHttpResponse must consume
> synchronous iterators in order to serve them asynchronously. Use an
> asynchronous iterator instead.
>
> This is because `FileResponse` is not async compatible (nor is that
> likely, since neither is `open()`).
>
> A new project with:
>

> {{{
> INSTALLED_APPS = [
> "daphne",
> ...
> ]
>
> ASGI_APPLICATION = "project.asgi.application"
> }}}
>
> `runserver`, and then visit any page serving static files such as
> `/admin/`.
>
> The fix is to have `ASGIStaticFilesHandler` adapt the iterator in the
> same way `StreamingHttpResponse` does.

New description:

 #33735 added async support to `StreamingHttpResponse` for Django 4.2.

 With Django 4.2rc1 and Daphne, `ASGIStaticFilesHandler ` raises a warning
 about the incorrect iterator type being used:

 > http/response.py:534: Warning: StreamingHttpResponse must consume
 synchronous iterators in order to serve them asynchronously. Use an
 asynchronous iterator instead.

 This is because `FileResponse` is not async compatible (nor is that
 likely, since neither is `open()`).

 A new project with:


 {{{
 INSTALLED_APPS = [
 "daphne",
 ...
 ]

 ASGI_APPLICATION = "project.asgi.application"
 }}}

 `runserver`, and then visit any page serving static files such as
 `/admin/`.

 The fix is to have `ASGIStaticFilesHandler` adapt the iterator in the same
 way `StreamingHttpResponse` does.

--

-- 
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/0107018704fd8a6b-b5309124-e503-4963-b45c-cf5a75ae3b69-00%40eu-central-1.amazonses.com.

Re: [Django] #34428: ASGIStaticFilesHandler raises warning.

[Django]

#34428: ASGIStaticFilesHandler raises warning.
-+-
 Reporter:  Carlton Gibson   |Owner:  Carlton
 |  Gibson
 Type:  Bug  |   Status:  assigned
Component:  contrib.staticfiles  |  Version:  4.2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by Carlton Gibson:

Old description:

> #33735 added async support to StreamingHttpResponse for Django 4.2.
>
> With Django 4.2rc1 and Daphne, ``` raises a warning about the incorrect
> iterator type being used:
>
> > http/response.py:534: Warning: StreamingHttpResponse must consume
> synchronous iterators in order to serve them asynchronously. Use an
> asynchronous iterator instead.
>
> This is because `FileResponse` is not async compatible (nor is that
> likely, since neither is `open()`).
>
> A new project with:
>

> {{{
> INSTALLED_APPS = [
> "daphne",
> ...
> ]
>
> ASGI_APPLICATION = "project.asgi.application"
> }}}
>
> `runserver`, and then visit any page serving static files such as
> `/admin/`.
>
> The fix is to have `ASGIStaticFilesHandler` adapt the iterator in the
> same way `StreamingHttpResponse` does.

New description:

 #33735 added async support to `StreamingHttpResponse` for Django 4.2.

 With Django 4.2rc1 and Daphne, `StreamingHttpResponse` raises a warning
 about the incorrect iterator type being used:

 > http/response.py:534: Warning: StreamingHttpResponse must consume
 synchronous iterators in order to serve them asynchronously. Use an
 asynchronous iterator instead.

 This is because `FileResponse` is not async compatible (nor is that
 likely, since neither is `open()`).

 A new project with:


 {{{
 INSTALLED_APPS = [
 "daphne",
 ...
 ]

 ASGI_APPLICATION = "project.asgi.application"
 }}}

 `runserver`, and then visit any page serving static files such as
 `/admin/`.

 The fix is to have `ASGIStaticFilesHandler` adapt the iterator in the same
 way `StreamingHttpResponse` does.

--

-- 
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/0107018704e9687d-f20d87e4-3d80-4733-ab11-aa94d0689566-00%40eu-central-1.amazonses.com.

[Django] #34429: Allow to set unusable password via admin UI

[Django]

#34429: Allow to set unusable password via admin UI
---+
   Reporter:  Tobias Bengfort  |  Owner:  nobody
   Type:  New feature  | Status:  new
  Component:  contrib.auth |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|
---+
 Django allows to have user accounts with unusable passwords, either
 because authentication uses a different mechanism (e.g. LDAP) or because
 the User object is still needed (e.g. because it is referenced by a
 ForeignKey) but the user should no longer be allowed to log in.

 However, this functionality is not available from the admin UI. When
 creating a user or changing the password I am forced to enter a password.

 I propose to make the password fields optional in the Admin UI and set an
 unusable password if they are blank.

 I am sorry if this has been discussed before. I looked before posting this
 but could not find anything.

-- 
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/0107018704e1dc20-32be7627-ff9a-4b24-9bb2-3a5db0cc2c22-00%40eu-central-1.amazonses.com.

Re: [Django] #34428: ASGIStaticFilesHandler raises warning.

[Django]

#34428: ASGIStaticFilesHandler raises warning.
-+-
 Reporter:  Carlton Gibson   |Owner:  Carlton
 |  Gibson
 Type:  Bug  |   Status:  assigned
Component:  contrib.staticfiles  |  Version:  4.2
 Severity:  Release blocker  |   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 Carlton Gibson):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/16670 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/0107018704cd2020-4d19f285-e12a-488d-9048-017abca6a528-00%40eu-central-1.amazonses.com.

[Django] #34428: ASGIStaticFilesHandler raises warning.

[Django]

#34428: ASGIStaticFilesHandler raises warning.
-+-
   Reporter:  Carlton|  Owner:  Carlton Gibson
  Gibson |
   Type:  Bug| Status:  assigned
  Component: |Version:  4.2
  contrib.staticfiles|
   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  |
-+-
 #33735 added async support to StreamingHttpResponse for Django 4.2.

 With Django 4.2rc1 and Daphne, ``` raises a warning about the incorrect
 iterator type being used:

 > http/response.py:534: Warning: StreamingHttpResponse must consume
 synchronous iterators in order to serve them asynchronously. Use an
 asynchronous iterator instead.

 This is because `FileResponse` is not async compatible (nor is that
 likely, since neither is `open()`).

 A new project with:


 {{{
 INSTALLED_APPS = [
 "daphne",
 ...
 ]

 ASGI_APPLICATION = "project.asgi.application"
 }}}

 `runserver`, and then visit any page serving static files such as
 `/admin/`.

 The fix is to have `ASGIStaticFilesHandler` adapt the iterator in the same
 way `StreamingHttpResponse` does.

-- 
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/0107018704cb9388-505cb9c7-0c13-4cf6-a760-51f087619519-00%40eu-central-1.amazonses.com.

Re: [Django] #33134: Circular contexts when rendering Form with BoundFields.

[Django]

#33134: Circular contexts when rendering Form with BoundFields.
-+-
 Reporter:  Mariusz Felisiak |Owner:  David
 |  Smith
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  4.0
 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 Carlton Gibson ):

 In [changeset:"051d5944f86400b9b3476db60bc73de7e9964810" 051d594]:
 {{{
 #!CommitTicketReference repository=""
 revision="051d5944f86400b9b3476db60bc73de7e9964810"
 Refs #33134, Refs #34077 -- Adjusted form rendering recursion test.

 Adjusted recursion depth test to use str() rather than the form or
 field’s render() method.
 }}}

-- 
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/0107018704a1fb59-8b429e16-5937-4755-bd61-9ce322caccb2-00%40eu-central-1.amazonses.com.

Re: [Django] #34077: Make BoundField renderable.

[Django]

#34077: Make BoundField renderable.
-+---
 Reporter:  David Smith  |Owner:  David Smith
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  4.1
 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
-+---

Comment (by Carlton Gibson ):

 In [changeset:"051d5944f86400b9b3476db60bc73de7e9964810" 051d594]:
 {{{
 #!CommitTicketReference repository=""
 revision="051d5944f86400b9b3476db60bc73de7e9964810"
 Refs #33134, Refs #34077 -- Adjusted form rendering recursion test.

 Adjusted recursion depth test to use str() rather than the form or
 field’s render() method.
 }}}

-- 
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/0107018704a1fb27-9166bc77-08e7-449b-84b1-48e7a3c7d5ad-00%40eu-central-1.amazonses.com.

Re: [Django] #34427: Improve error message for incorrect context processors (was: Improve error message for bad context processors)

[Django]

#34427: Improve error message for incorrect context processors
-+--
 Reporter:  Adam Johnson |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Template system  |  Version:  dev
 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
-+--

-- 
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/01070187049d25a7-4f4a711a-382e-45b4-b142-cd4204a53714-00%40eu-central-1.amazonses.com.

[Django] #34427: Improve error message for bad context processors

[Django]

#34427: Improve error message for bad context processors
---+
   Reporter:  Adam Johnson |  Owner:  nobody
   Type:  New feature  | Status:  new
  Component:  Template 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|
---+
 If you write a template context processor but return the wrong type, for
 example `None` by missing the return statement:

 {{{
 def data(request):
 data = {"something": True}
 }}}

 Then currently the error message is very mysterious:

 {{{
 Internal Server Error: /
 Traceback (most recent call last):
   ...
   File "//site-packages/django/template/backends/django.py", line 61,
 in render
 return self.template.render(context)
^
   File "//site-packages/django/template/base.py", line 173, in render
 with context.bind_template(self):
   File "/.../lib/python3.11/contextlib.py", line 137, in __enter__
 return next(self.gen)
^^
   File "//site-packages/django/template/context.py", line 254, in
 bind_template
 updates.update(processor(self.request))
 TypeError: 'NoneType' object is not iterable
 }}}

 If a view returns the wrong type, Django raises a nice error message:

 {{{
 The view example.views.index didn't return an HttpResponse object. It
 returned None instead.
 }}}

 I suggest we do the same for context processors. If we use try/except
 around the `updates.update()` line, it will not slow down normal
 processing any noticeable amount, thanks to Python 3.11's “zero-cost”
 exception handling: https://docs.python.org/3.11/whatsnew/3.11.html#misc

-- 
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/01070187049cdbe2-91ab6e34-a258-4546-853e-4c3834fc421d-00%40eu-central-1.amazonses.com.

Re: [Django] #34402: Admin search_fields crashes for inherited model and __iexact lookup.

[Django]

#34402: Admin search_fields crashes for inherited model and __iexact lookup.
+-
 Reporter:  Pavel Pančocha  |Owner:  Rahmat Faisal
 Type:  Bug |   Status:  assigned
Component:  contrib.admin   |  Version:  3.2
 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 Rahmat Faisal):

 * owner:  nobody => Rahmat Faisal
 * 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/010701870479d4fe-3a38fc02-27a9-48cf-a7ac-66057613781c-00%40eu-central-1.amazonses.com.

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

[Django]

#34388: Added support for direct usage of Choices classes on model fields
-+-
 Reporter:  T. Franzel   |Owner:  T.
 |  Franzel
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 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/010701870438e8f5-16b6eccc-f2f9-48c1-835a-df028ecc9d8a-00%40eu-central-1.amazonses.com.

Re: [Django] #34426: Pass the BoundField instance to the Widget.render

[Django]

#34426: Pass the BoundField instance to the Widget.render
--+--
 Reporter:  Christophe Henry  |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  Forms |  Version:  4.2
 Severity:  Normal|   Resolution:  duplicate
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by Mariusz Felisiak):

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


Comment:

 Duplicate of #33166 (see also #34077).

-- 
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/01070187042c6bf9-6e8f150d-fc83-49c0-bd4d-2d04a162ba73-00%40eu-central-1.amazonses.com.

[Django] #34426: Pass the BoundField instance to the Widget.render

[Django]

#34426: Pass the BoundField instance to the Widget.render
+
   Reporter:  Christophe Henry  |  Owner:  nobody
   Type:  New feature   | Status:  new
  Component:  Forms |Version:  4.2
   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 |
+
 Django 4's form rendering API is nice, but lacking a important feature to
 me: the `Widget` used to render a particular `Field` doesn't have any
 access to the corresponding `BoundField`. This makes rendering the field,
 label, potential error messages altogether as well as more more complex
 structures — like fields with subfields, for instance — impossible to
 render atomically within the widget. If you want to do that, you're forced
 to go up to the `Form`'s template itself.

 My opinion is that
 
[[https://docs.djangoproject.com/en/4.1/ref/forms/widgets/#django.forms.Widget.render|`Widget.render`]]
 should be passed the corresponding `BoundField` instance.

 This would, I think, have 2 benefits:

 1. allow easier rendering of complex widgets like
 [https://github.com/django/django/blob/main/django/forms/widgets.py#L585
 ChoiceWidget] using an iteration on the
 [https://github.com/django/django/blob/main/django/forms/boundfield.py#L59-L60
 BoundField]
 ([https://docs.djangoproject.com/en/4.1/ref/forms/widgets/#radioselect
 which is what's documented] and would allow unification with
 [https://github.com/django/django/blob/main/django/forms/widgets.py#L616-L659
 ChoiceWidget.options and ChoiceWidget.optgroups])

 2. allow rendering together `Form` fields that are related since
 `BoundField` has access to the parent `Form` (for instance a form with
 three options: email, phone, and other, respectively related to an email
 input, a phone input and a text input that are displayed below each).

 P.S.: This is a feature request but I'm still opening a bug here since I
 can't join the django-developers mailing-list without a Google account.

-- 
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/010701870412428a-03e3752e-6a3b-4b5b-b805-51da33cefc56-00%40eu-central-1.amazonses.com.

Re: [Django] #34417: AlterField migration on ForeignKey field re-creates foreign key constraints unnecessarily

[Django]

#34417: AlterField migration on ForeignKey field re-creates foreign key 
constraints
unnecessarily
-+-
 Reporter:  Ömer Faruk Abacı |Owner:  Deniz
 Type:   |  Altun
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  4.1
 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 Deniz Altun):

 * owner:  nobody => Deniz Altun
 * 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/0107018703c0a77d-b0bdcdbb-0c72-45ab-b49f-83ca484c82e0-00%40eu-central-1.amazonses.com.

Re: [Django] #28283: _changeform_view sends wrong object after ModelForm validation

[Django]

#28283: _changeform_view sends wrong object after ModelForm validation
---+
 Reporter:  ddein  |Owner:  (none)
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  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:  ddein => (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/0107018703a613da-37593f88-fa8a-4e04-8124-d67cc703d4c4-00%40eu-central-1.amazonses.com.

Re: [Django] #19303: ModelAdmin.formfield_overrides is ignored for fields with choices

[Django]

#19303: ModelAdmin.formfield_overrides is ignored for fields with choices
---+
 Reporter:  Ben Davis  |Owner:  (none)
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  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):

 * 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/0107018703a477e0-d5f3ea88-3315-4b97-afd5-c41cf933e20e-00%40eu-central-1.amazonses.com.

Re: [Django] #19303: ModelAdmin.formfield_overrides is ignored for fields with choices

[Django]

#19303: ModelAdmin.formfield_overrides is ignored for fields with choices
---+
 Reporter:  Ben Davis  |Owner:  (none)
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  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:  Łukasz Balcerzak => (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/0107018703a46b7d-5df36b93-a64d-4d1d-8e2f-7c53b0aa0b5b-00%40eu-central-1.amazonses.com.

Re: [Django] #10327: Pass document.domain to popup windows in admin

[Django]

#10327: Pass document.domain to popup windows in admin
--+
 Reporter:  Joost Cassee  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  contrib.admin |  Version:  dev
 Severity:  Normal|   Resolution:  wontfix
 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 Mariusz Felisiak):

 * status:  new => closed
 * type:  Bug => Cleanup/optimization
 * resolution:   => wontfix


Comment:

 The `document.domain` setter is [https://developer.mozilla.org/en-
 US/docs/Web/API/Document/domain#deprecation deprecated] and dangerous.

-- 
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/010701870397545a-eb16c4af-355c-4f2a-b0f7-6b39df137396-00%40eu-central-1.amazonses.com.

Re: [Django] #20752: Error signals are not reliable, especially when dealing with database errors

[Django]

#20752: Error signals are not reliable, especially when dealing with database
errors
-+-
 Reporter:  tal@…|Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  HTTP handling|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  signals errors   | Triage Stage:  Accepted
  databaseError  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  schacki => (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/0107018703865a3e-4ddedd75-bffc-4181-aaaf-3a50441c97d6-00%40eu-central-1.amazonses.com.

Re: [Django] #23843: Test failures on Oracle/Python3

[Django]

#23843: Test failures on Oracle/Python3
-+-
 Reporter:  Shai Berger  |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  Shai Berger => (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/010701870385fd73-1745fa40-8d1b-48c3-b697-579043cc3c4f-00%40eu-central-1.amazonses.com.

Re: [Django] #25656: Recent Actions admin section contains link to edit form even when user does not have edit permission

[Django]

#25656: Recent Actions admin section contains link to edit form even when user 
does
not have edit permission
+
 Reporter:  Anton Baklanov  |Owner:  (none)
 Type:  Bug |   Status:  new
Component:  contrib.admin   |  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:  Anton Baklanov => (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/0107018703858bcb-dc07655c-524d-4f21-8fa9-f1577a2ddffb-00%40eu-central-1.amazonses.com.

Re: [Django] #27460: Allow declaring a GenericRelation from an abstract model to another abstract model

[Django]

#27460: Allow declaring a GenericRelation from an abstract model to another
abstract model
-+-
 Reporter:  Wolfgang Grim|Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  GenericRelation, | Triage Stage:  Accepted
  Abstract, ContentFramework |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  Alex Hill => (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/0107018703849463-66ff7bfc-b83f-4ba9-b5f8-9bb823d67c56-00%40eu-central-1.amazonses.com.

Re: [Django] #27447: Provide an easy way to test sending of signals

[Django]

#27447: Provide an easy way to test sending of signals
---+
 Reporter:  James Bennett  |Owner:  (none)
 Type:  New feature|   Status:  new
Component:  Testing framework  |  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 Mariusz Felisiak):

 * owner:  James Bennett => (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/01070187038453ac-b9c73bef-5326-401f-85c3-ded31bc1f695-00%40eu-central-1.amazonses.com.

Re: [Django] #22055: 404 page does not display stack trace when Resolver404 is raised from a view

[Django]

#22055: 404 page does not display stack trace when Resolver404 is raised from a
view
--+
 Reporter:  Grzegorz Nosek|Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (URLs)   |  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:  Grzegorz Nosek => (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/010701870383dc76-5d52e2d3-1a02-4f9e-ac21-611f361f11c8-00%40eu-central-1.amazonses.com.

Re: [Django] #22055: 404 page does not display stack trace when Resolver404 is raised from a view

[Django]

#22055: 404 page does not display stack trace when Resolver404 is raised from a
view
--+
 Reporter:  Grzegorz Nosek|Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (URLs)   |  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):

 * 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/010701870383e85a-b32957d6-be5d-494b-ade0-23c0c90943ad-00%40eu-central-1.amazonses.com.

Re: [Django] #27923: Add form signals (pre_init, post_init, pre_clean, post_clean, etc.)

[Django]

#27923: Add form signals (pre_init, post_init, pre_clean, post_clean, etc.)
+
 Reporter:  David Seddon|Owner:  (none)
 Type:  New feature |   Status:  new
Component:  Forms   |  Version:
 Severity:  Normal  |   Resolution:
 Keywords:  forms, signals  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+
Changes (by Mariusz Felisiak):

 * owner:  luojiebin => (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/0107018703839615-59fa882f-1e7f-4808-8210-8cb5a14b1507-00%40eu-central-1.amazonses.com.

Re: [Django] #22479: Support byte range requests in django.views.static.serve

[Django]

#22479: Support byte range requests in django.views.static.serve
---+
 Reporter:  Nick Sandford  |Owner:  (none)
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  Version:  dev
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Mariusz Felisiak):

 * owner:  Nick Sandford => (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/01070187038373e1-3d9e7c3c-0e21-4572-ba91-892d79beeb54-00%40eu-central-1.amazonses.com.

Re: [Django] #27487: ModelAdmin.formfield_overrides on ManyToManyField isn't compatible with CheckboxSelectMultiple

[Django]

#27487: ModelAdmin.formfield_overrides on ManyToManyField isn't compatible with
CheckboxSelectMultiple
--+
 Reporter:  nrogers64 |Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  1.10
 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 Mariusz Felisiak):

 * owner:  Adonys Alea Boffill => (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/0107018703834ba3-a3ca398d-8a80-4353-b31f-86b3ce2e3d54-00%40eu-central-1.amazonses.com.

Re: [Django] #27833: prefetch_related fails with SQLite when used with 1000 parent records

[Django]

#27833: prefetch_related fails with SQLite when used with 1000 parent records
-+-
 Reporter:  Jason Barnabe|Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  Raphael Michel => (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/01070187038253d5-243c6227-c24a-4b21-9b05-def2c8067ddc-00%40eu-central-1.amazonses.com.

Re: [Django] #15855: cache_page decorator bypasses any Vary headers set in middleware

[Django]

#15855: cache_page decorator bypasses any Vary headers set in middleware
-+
 Reporter:  Carl Meyer   |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Core (Cache system)  |  Version:
 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 Mariusz Felisiak):

 * owner:  Rinat Khabibiev => (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/010701870382376a-5ce7baf6-4fe7-4574-9581-5cb4878bf0e4-00%40eu-central-1.amazonses.com.

Re: [Django] #9739: Admin does not correctly prefill DataTimeField from URL

[Django]

#9739: Admin does not correctly prefill DataTimeField from URL
---+
 Reporter:  gilhad |Owner:  (none)
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.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 Mariusz Felisiak):

 * owner:  Ridley Larsen => (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/010701870381385b-ec8462e4-8241-4ee6-9564-7863fe9ac878-00%40eu-central-1.amazonses.com.

Re: [Django] #20372: using registration/logged_out.html template overrides admin logout

[Django]

#20372: using registration/logged_out.html template overrides admin logout
--+
 Reporter:  tomerz@…  |Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Mariusz Felisiak):

 * owner:  Alexis Bellido => (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/010701870380e242-689c1e9f-afe2-477f-8a10-df02ebcc7366-00%40eu-central-1.amazonses.com.

Re: [Django] #31539: Add support for bulk operations on reverse many-to-one manager

[Django]

#31539: Add support for bulk operations on reverse many-to-one manager
-+-
 Reporter:  Baptiste Mispelon|Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  Baptiste Mispelon => (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/01070187037fe2e5-ed101c93-7531-4bb2-8449-c57ad7d6bf1e-00%40eu-central-1.amazonses.com.

Re: [Django] #29771: Support database-specific syntax for bulk_update

[Django]

#29771: Support database-specific syntax for bulk_update
-+-
 Reporter:  Tom Forbes   |Owner:  (none)
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  Tom Forbes => (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/01070187037f727d-505b2a27-2afe-4681-8269-4f232d1adb0a-00%40eu-central-1.amazonses.com.

Re: [Django] #21076: Offer the ability to store a hash of session IDs rather than the ID itself

[Django]

#21076: Offer the ability to store a hash of session IDs rather than the ID 
itself
--+
 Reporter:  Tim Graham|Owner:  (none)
 Type:  New feature   |   Status:  new
Component:  contrib.sessions  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Mariusz Felisiak):

 * owner:  Mark => (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/01070187037ee89b-55a418fe-49e5-4750-9e73-0ea5b291d170-00%40eu-central-1.amazonses.com.

Re: [Django] #25281: Permission strings don't uniquely identify permissions

[Django]

#25281: Permission strings don't uniquely identify permissions
-+-
 Reporter:  Przemysław   |Owner:  (none)
  Pietrzkiewicz  |
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.auth |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  tsyplakou => (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/01070187037eb22d-441905e8-04fb-4650-823a-46655e6e8706-00%40eu-central-1.amazonses.com.

Re: [Django] #26223: Squashing migrations with preserve_default=False keeps the default

[Django]

#26223: Squashing migrations with preserve_default=False keeps the default
-+
 Reporter:  Bartek Wójcicki  |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Migrations   |  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 Mariusz Felisiak):

 * owner:  Vytis Banaitis => (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/01070187037d3b9d-14be15d5-b904-4fae-851b-9cff7e93bcd2-00%40eu-central-1.amazonses.com.

Re: [Django] #31932: Unique checking in formsets should exclude forms marked for deletion.

[Django]

#31932: Unique checking in formsets should exclude forms marked for deletion.
-+-
 Reporter:  Marco Beri   |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  3.1
 Severity:  Normal   |   Resolution:
 Keywords:  formset, inline, | Triage Stage:  Accepted
  unique_together|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  Aditya parashar => (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/01070187037cb4b5-fe6b81b9-28e3-43d3-9441-25c469347d64-00%40eu-central-1.amazonses.com.

Re: [Django] #28872: JSONField __in operator breaks when given a values_list()

[Django]

#28872: JSONField __in operator breaks when given a values_list()
-+-
 Reporter:  Jerome Leclanche |Owner:  (none)
 Type:  Bug  |   Status:  new
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:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  VCAMP => (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/01070187037c2025-c2ec9ac3-5167-4d42-ba1c-daeb55ecdeeb-00%40eu-central-1.amazonses.com.

Re: [Django] #22125: Unnecessary creation of index for ManyToManyField

[Django]

#22125: Unnecessary creation of index for ManyToManyField
-+-
 Reporter:  tbhtan3@…|Owner:  (none)
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  db-indexes   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
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/01070187037bdb73-6cb6c961-281a-4852-954d-b54d91c537d9-00%40eu-central-1.amazonses.com.

Re: [Django] #22125: Unnecessary creation of index for ManyToManyField

[Django]

#22125: Unnecessary creation of index for ManyToManyField
-+-
 Reporter:  tbhtan3@…|Owner:  (none)
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  db-indexes   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  bwreilly => (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/01070187037bcd23-8915645a-5810-4d2b-9248-a788bbebeaf3-00%40eu-central-1.amazonses.com.

Re: [Django] #21461: Add pre_update and post_update signals

[Django]

#21461: Add pre_update and post_update signals
-+-
 Reporter:  loic84   |Owner:  (none)
 Type:  New feature  |   Status:  new
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:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  loic84 => (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/010701870379ae49-1eb4d8dc-6c41-4033-b019-42b93ee01154-00%40eu-central-1.amazonses.com.

Re: [Django] #28048: Allow generic date views to use related fields as date_field

[Django]

#28048: Allow generic date views to use related fields as date_field
-+
 Reporter:  Lefteris Nikoltsios  |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Generic views|  Version:  1.11
 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 Mariusz Felisiak):

 * owner:  Lefteris Nikoltsios => (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/010701870378641f-f1b670c6-8976-497a-a3b5-00d09c629fbb-00%40eu-central-1.amazonses.com.

Re: [Django] #28384: ModelAdmin.lookup_allowed() incorrectly raises DisallowedModelAdminLookup lookup with foreign key as primary key

[Django]

#28384: ModelAdmin.lookup_allowed() incorrectly raises 
DisallowedModelAdminLookup
lookup with foreign key as primary key
--+---
 Reporter:  elliott-omosheye  |Owner:  Sarah Boyce
 Type:  Bug   |   Status:  assigned
Component:  contrib.admin |  Version:  1.11
 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 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/010701870371b210-7883f7ff-5aae-4890-9729-cb6361b38e53-00%40eu-central-1.amazonses.com.

Re: [Django] #24686: Support for Moving a model between two Django apps

[Django]

#24686: Support for Moving a model between two Django apps
---+---
 Reporter:  Alex Rothberg  |Owner:  Durval Carvalho
 Type:  New feature|   Status:  assigned
Component:  Migrations |  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 Mariusz Felisiak):

 * needs_docs:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070187032b73cc-3ba1d6a4-a2f6-47ad-9a75-b9ddf90aeddb-00%40eu-central-1.amazonses.com.

Re: [Django] #34409: Examples of fetching raw SQL don't work for non-unique column names.

[Django]

#34409: Examples of fetching raw SQL don't work for non-unique column names.
-+-
 Reporter:  Jesper Olsson|Owner:  Jesper
 Type:   |  Olsson
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  4.1
 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
 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/16665 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/0107018702fcbdd7-69e8b6e1-37e7-41dc-a4b5-bd0c3e03e436-00%40eu-central-1.amazonses.com.