Hey there,
> Not that much with a 50 lines function. that could easily become a
maintenance burden.
> what do you think about code duplication of async function ? (please
point me to existing threads if the discussion already occurred)
I flagged this problem
in
y? It's nicer, better contained, and we more likely to catch
> interested eyes.
>
> Thanks for pursuing this!
>
> On Thu, 9 Feb 2023 at 23:38, Jon Janzen <mailto:j...@jonjanzen.com>> wrote:
>> Hey Carlton,
>>
>> Thanks for your thoughtful comm
seems like
> an orthogonal issue while https://code.djangoproject.com/ticket/31949 is
> pending, am I missing something here? Do I need to consider decorators in
> this proposal?
>
> I don't think they're dependent.
>
>
> Kind Regards,
>
> Carlton
>
> On Mon, 6 Feb 20
rete plan. (We'd likely just
> close it as wontfix unless there's a specific idea on the table anyway, so
> it's just noise at that point.)
>
> I hope that makes sense.
>
> Kind Regards,
>
> Carlton
>
> On Mon, 28 Nov 2022 at 16:53, Jon Janzen <mailto:j...@jonjanzen
Hey Carlton,
There's: https://code.djangoproject.com/ticket/31949 "Allow builtin view
> decorators to be applied directly to async views."
> I think this is likely the next step.
>
> There's a PR for that, which I think took a too complex approach (see
> discussion). A simpler (more inline) take
Hey everyone,
Sorry if I'm not following correct protocol on this or if this has already
been discussed elsewhere, but is there any consensus about (or needed for)
creating async versions of contrib packages?
My personal interest in this is about django.contrib.auth (login,
authenticate,
