Closed nite closed 6 years ago
So that, if aiohttp does a major version upgrade (which implies breaking changes), it won't break!
I shall push out a version that uses aiohttp 3 in the next day or so.
On 15 March 2018 at 12:27, Andrew Clancy notifications@github.com wrote:
Is there any specific reason aiohttp-wsgi is pinned to aiohttp<3 (in setup.py)?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/etianen/aiohttp-wsgi/issues/22, or mute the thread https://github.com/notifications/unsubscribe-auth/AAJFCBrG0M9sH-Vup01WunG8P9BJ3SzLks5tel4igaJpZM4SsD3D .
Fixed in 0.8.
Is there any specific reason aiohttp-wsgi is pinned to
aiohttp<3
(in setup.py) @etianen ?