<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Timeouts on Nalar</title>
    <link>https://nalar.dev/tags/timeouts/</link>
    <description>Recent content in Timeouts on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 08 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/timeouts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Budget Async Work with asyncio.timeout</title>
      <link>https://nalar.dev/budget-async-work-with-asyncio-timeout/</link>
      <pubDate>Tue, 08 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/budget-async-work-with-asyncio-timeout/</guid>
      <description>&lt;p&gt;Timeouts in asynchronous programs are easy to scatter and surprisingly hard to compose. A service call gets five seconds, a database query gets five more, and a retry gets another five. Each individual limit looks reasonable, yet the whole request can run far beyond the caller&amp;rsquo;s budget.&lt;/p&gt;&#xA;&lt;p&gt;Python 3.11 added &lt;code&gt;asyncio.timeout()&lt;/code&gt;, an asynchronous context manager that makes a different model practical: put a time budget around a block of work, not just around one awaitable.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
