<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Graphlib on Nalar</title>
    <link>https://nalar.dev/tags/graphlib/</link>
    <description>Recent content in Graphlib on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 04 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/graphlib/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Order Dependency-Driven Work in Python with graphlib.TopologicalSorter</title>
      <link>https://nalar.dev/order-dependency-driven-work-in-python-with-graphlib-topologicalsorter/</link>
      <pubDate>Fri, 04 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/order-dependency-driven-work-in-python-with-graphlib-topologicalsorter/</guid>
      <description>&lt;p&gt;Many automation tasks are not really lists. They are dependency graphs.&lt;/p&gt;&#xA;&lt;p&gt;A deployment may need a database migration before the API starts, while static assets can build independently. A data pipeline may need two source extracts before a join can run. A build system may have several targets that become runnable as soon as their prerequisites finish.&lt;/p&gt;&#xA;&lt;p&gt;If you encode this work as one hand-written sequence, you hide the real constraint: &lt;strong&gt;which tasks depend on which other tasks&lt;/strong&gt;. That makes the sequence harder to change and can prevent independent work from running concurrently.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
