Hi folks, I was going to write this in django developers, but looks like I
might have found a small area for improvement for the async_unsafe
decorator, but first let me give you a bit of background:
We're upgrading to Django 3.0 and we've been encountering this error on ci
when running all
>
> I was going to write this in django developers
This is django-developers?
which creates a new loop every time, which seems to be the cause of the too
> many files open.
>
Can you give a bit more explanation how it creates a new loop every time?
Two successive calls to get_event_loop() in
On Thu, 8 Oct 2020 at 22:28, Adam Johnson wrote:
> I was going to write this in django developers
>
>
> This is django-developers?
>
I meant django-users, sorry :D
> which creates a new loop every time, which seems to be the cause of the
>> too many files open.
>>
>
> Can you give a bit more
I would definitely be in favor of an opt-in: it would give developers
time to move to the new system at their convenience.
Example: we're about to try and tackle the TZ issue in our apps and we
want to do it "globally" with one definitive solution. I'd much rather
do it on a library that is
