OK, yes, that's probably right. Had #34063 been reported during the 3.1 cycle it would have been a release blocker. As it was, it wasn't reported until 4.0 (when main was already 4.1) so two cycles later. As such it no longer qualifies for a backport.
It's frustrating when this happens, but the backport policy has proven its worth time and again. I **really** don't see the case for making an exception here. (The policy has more value than the inconvenience in any of these cases, or even all of them summed.) > As it was, it wasn't reported until 4.0 ... I think the bottomline is people are only starting to use this stuff now. It's still experimental, for whatever that means, and there simply are and will be rough edges. I'd be very happy to think about how we should message that better — a big sign saying "Still in development: if you want to use async, be on the latest versions" would be fine in my opinion. I think we've been pretty upfront that that's the case. Adding the support here is difficult and slow enough. Backporting fixes to discovered bugs, outside the established policy, is making an unrealistic burden for ourselves. On Fri, 30 Dec 2022 at 10:13, James Bennett <ubernost...@gmail.com> wrote: > On Fri, Dec 30, 2022 at 1:09 AM Carlton Gibson <carlton.gib...@gmail.com> > wrote: > > All you're talking about is adding this to your test cases right? > > > > # Work around Django #34063 until 4.2. > > request.body > > As far as I can tell it needs to go in whatever code will *read* > request.POST, not the code that generates the request. So that means a > no-op "request.body" in every view and every middleware that might > read request.POST. And that includes Django's own built-in views > (including generic views) and any built-in async-supporting > middlewares, if they have the misfortune to get called on the async > path from an AsyncClient-initiated request. > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CAL13Cg_1MMt2DbcC%2B4Vfzi83g_U-bBNj2-J92Y1NWTvAS9c1Ww%40mail.gmail.com > . > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJwKpyTCeMvXsxHwENYf0pEw2ySBXOadBEe_EXC04SndSk%3D6bQ%40mail.gmail.com.
