<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Subprocess on Nalar</title>
    <link>https://nalar.dev/tags/subprocess/</link>
    <description>Recent content in Subprocess 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/subprocess/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Avoid Subprocess Pipe Deadlocks in Python</title>
      <link>https://nalar.dev/avoid-subprocess-pipe-deadlocks-in-python/</link>
      <pubDate>Fri, 04 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/avoid-subprocess-pipe-deadlocks-in-python/</guid>
      <description>&lt;p&gt;Launching a command from Python is easy. Capturing its output is also easy. The trouble starts when a parent process waits for a child while the child is waiting for the parent to read from a pipe.&lt;/p&gt;&#xA;&lt;p&gt;That circular wait is a &lt;strong&gt;deadlock&lt;/strong&gt;: neither process can make progress even though neither has crashed.&lt;/p&gt;&#xA;&lt;p&gt;This problem is especially confusing because the same code may work during testing and hang only when a command produces more output. Small output fits in an operating-system pipe buffer. Larger output can fill that buffer and expose the incorrect coordination.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
