> This could also be resolved with any &/or all i.e.:
>
> if any([foo in foobar, bar in foobar, baz in foobar]):
>
> Or even:
>
> if any([l in foobar for l in [foo, bar, baz]]
The goal was to have simpler syntax not a harder one, even if this already
works this can't be said simpler (I eve
> It's much simpler to rename April 1 to February 29.
That will create a gap of one 1 day beetween shity regular callendar and
our new one for 2 month.
An algorithm distributing leap seconds near 1 first april, is maybe more
complicated but reduce side effect with the world.
__
I was doing some async networking and I wondered, why I have to use 2
different api for making the same things in async or sync regime.
Even if we make 2 perfectly identical api (except function will be sync and
async), it will still 2 different code).
So I first thinked to allow await in syncrono
