What is this?
aiohttp is an asynchronous HTTP client and server framework built on asyncio: one Python package for making HTTP requests and for building web applications, with WebSockets supported out of the box.
aiohttp is an asynchronous HTTP client and server framework built on asyncio: one Python package for making HTTP requests and for building web applications, with WebSockets supported out of the box.Is it a library I import into my code, or a framework that runs my whole app?Both ship in one package: as a client it is a library you call (aiohttp.ClientSession); as a server it is a framework — you write handlers, add routes to a web.Application and run it with web.run_app.
Both ship in one package: as a client it is a library you call (aiohttp.ClientSession); as a server it is a framework — you write handlers, add routes to a web.Application and run it with web.run_app.How do I make my first request with it?Install from PyPI (pip install aiohttp), then work inside an async function: open a ClientSession, call session.get(url) as a response and await response.text() for the body.
Install from PyPI (pip install aiohttp), then work inside an async function: open a ClientSession, call session.get(url) as a response and await response.text() for the body.What does it depend on besides Python itself?Three required packages: multidict, yarl and frozenlist. Optionally add aiodns — the README calls it highly recommended for speed.
Three required packages: multidict, yarl and frozenlist. Optionally add aiodns — the README calls it highly recommended for speed.I already use requests — is switching painful?aiohttp code is asynchronous, so the same job takes more lines than with requests — the README even links a 'why we need so many lines' explainer for people coming from requests.
aiohttp code is asynchronous, so the same job takes more lines than with requests — the README even links a 'why we need so many lines' explainer for people coming from requests.Can I build a web server with it, not just call other APIs?Yes — handlers are plain async functions: register them on a web.Application with routes (path segments like /{name} work) and start it all with web.run_app(app). Middleware and pluggable routing are built in.
Yes — handlers are plain async functions: register them on a web.Application with routes (path segments like /{name} work) and start it all with web.run_app(app). Middleware and pluggable routing are built in.Does it handle WebSockets on both ends?Yes — client and server WebSocket support is out of the box, the README's server example is literally an echo WebSocket handler, and the async API is advertised as avoiding callback hell.
Yes — client and server WebSocket support is out of the box, the README's server example is literally an echo WebSocket handler, and the async API is advertised as avoiding callback hell.Do I need to know asyncio before touching it?Yes — aiohttp is built for asyncio, so you write async def coroutines with await and kick them off with asyncio.run(main()), exactly as the getting-started example does.
Yes — aiohttp is built for asyncio, so you write async def coroutines with await and kick them off with asyncio.run(main()), exactly as the getting-started example does.Is it actually fast?The README publishes no numbers of its own — it just points readers interested in efficiency to the benchmark list the AsyncIO community maintains on the official wiki.
The README publishes no numbers of its own — it just points readers interested in efficiency to the benchmark list the AsyncIO community maintains on the official wiki.Which topics is it in?asyncio, websockets, http-server, http-client, middleware, concurrency, async, web-framework, websocket, http, rest-api, hacktoberfest
asyncio, websockets, http-server, http-client, middleware, concurrency, async, web-framework, websocket, http, rest-api, hacktoberfest