Hi, I don't know if it'll help much, but I've also gotten this bug and have resolved it by manually upgrading python3-trio with pip to its latest version, overriding system's installed version (which is 0.13 last I checked).
pip install trio==0.18.0 Pretty sure the s3ql release notes for 3.7 suggests anything after trio 0.9 is supported, but perhaps there's a bug in there somewhere? Regards, Lorentz
