<story><title>Show HN: HTTP/2 Python-Asyncio Web Microframework</title><url>https://gitlab.com/pgjones/quart</url></story><parent_chain></parent_chain><comment><author>tomchristie</author><text>Neat, good to see more `asyncio` frameworks coming along.&lt;p&gt;Python&amp;#x27;s going to have a bit of an awkward time with two completely different sets of ecosystem for threaded vs. asyncio approaches, but it&amp;#x27;s necessary progress.&lt;p&gt;One thing I&amp;#x27;d be really keen to see is asyncio frameworks starting to consider adopting ASGI as a common interface. Each of quart, sanic, aiohttp currently all have their own gunicorn worker classes, http parsing, and none share the same common interface for handling the request&amp;#x2F;response interface between server and application.&lt;p&gt;It&amp;#x27;s a really high barrier to new asyncio frameworks, and it means we&amp;#x27;re not able to get shared middleware, such as WSGI&amp;#x27;s whitenoise or Werkzeug debugger, or the increased robustness that shared server implementations would tend to result in.&lt;p&gt;Would be interested to know what OP&amp;#x27;s position on this is?</text></comment>
<story><title>Show HN: HTTP/2 Python-Asyncio Web Microframework</title><url>https://gitlab.com/pgjones/quart</url></story><parent_chain></parent_chain><comment><author>mixmastamyk</author><text>Isn&amp;#x27;t this what sanic was supposed to be?&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;channelcat&amp;#x2F;sanic&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;channelcat&amp;#x2F;sanic&lt;/a&gt;</text></comment>