Hi
Today I've added a couple of lines in my source code, and I'm very ashamed of
it.
it "runs", and I know what it does (for now), but it's "too clever".
I have "abused" the "else" clause of the loops to makes a break "broke" more
loops
for i in range(10):
print(f'i: {i}')
f
Il giorno martedì 18 settembre 2018 17:36:16 UTC+2, vito.d...@gmail.com ha
scritto:
> > > is there a way to "convert" a "normal" decorator in one that can handle
> > > async functions?
> > In general? No.
> Ouch.
>
> I'm new to the "async" world, but so this mean that all of the (appliable)
>
Il giorno martedì 18 settembre 2018 17:15:22 UTC+2, Thomas Jollans ha scritto:
> > but I cannot rewrite this library.
>
> Perhaps not, but surely you can write your own decorator that does
> whatever this library's decorator does for async functions? Presumably
> you have the code...
well, maybe
Hi.
Let's say I have this library that expose a decorator; it's meant to be used
with normal functions.
but I have to "apply" the decorator to an async function.
>From what I understand I cannot "really" wait for this decorated async
>function, as it's not really "async", and, from a simple tes
