Facing this issue with any version of aiohttp starting from 3.4.0 and with recently released yarl 1.5.0.
Using previous yarl==1.4.2 solves this issue (error is gone).
Thought it was old bug bubbling out: aio-libs/aiohttp#1364, but it seems that this issue is new.
Facing this issue with any version of aiohttp starting from 3.4.0 and with recently released yarl 1.5.0.
Using previous yarl==1.4.2 solves this issue (error is gone).
Thought it was old bug bubbling out: aio-libs/aiohttp#1364, but it seems that this issue is new.