Happy New Year!
I've been reading this thread with keen interest since James first brought it
up. I think James's rationale is on point and that the back port to fix the bug
needs to be done.
To the future of async,
Matthew
-Original Message-
From: django-developers@googlegroups.com
On Sat, Dec 31, 2022 at 2:12 AM 'Adam Johnson' via Django developers
(Contributions to Django itself)
wrote:
> In the past I have also been frustrated at particular bug fixes not being
> backported. But I've gradually come to appreciate just how valuable the
> backport policy is. It keeps
Your proposal is quite niche: it only shortens the creation of a Manager
class when you need to add a single filter() call. The function seems like
it might be a useful helper within a project, if you use many such
managers. But custom managers might use any queryset methods, or other
logic. I've
This thread got too long too fast: it's a hell of a lot to catch up on. In
the future, please can we all let things sit for a bit so other voices can
chime in, especially when the issue has concretely affected very few users.
In the past I have also been frustrated at particular bug fixes not
On Fri, Dec 30, 2022 at 11:22 PM Carlton Gibson
wrote:
> Under normal circumstances you just use the sync Client, as you've always
> done. `response = client.get(`/my-async-view/`)`.
> Django handles that the **view** is async for you.
>
> It's only if you need to write an actual **async test**,
