<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pip on Andre&#39;s blog</title>
    <link>https://www.baryudin.com/tags/pip/</link>
    <description>Recent content in Pip on Andre&#39;s blog</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Sun, 04 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.baryudin.com/tags/pip/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Great Python Package Manager Wars: A Brief and Slightly Exhausted History</title>
      <link>https://www.baryudin.com/blog/python-package-manager-wars-history/</link>
      <pubDate>Sun, 04 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://www.baryudin.com/blog/python-package-manager-wars-history/</guid>
      <description>&lt;p&gt;Python is a fine language if your heart belongs to scripting and you&amp;rsquo;d rather not wrestle a type checker into submission every Tuesday afternoon. Quick-and-dirty automation, a proof of concept you&amp;rsquo;ll swear is temporary, a small website that somehow stays up for six years. Python handles all of that with a shrug and a smile.&lt;/p&gt;&#xA;&lt;p&gt;Now, I&amp;rsquo;ll say the quiet part: I don&amp;rsquo;t think Python is the right tool for very large, very serious engineering undertakings. But plenty of organisations disagree, or at least disagree in practice. Entire ecosystems, sprawling internal platforms, data pipelines the size of small rivers, all written in Python. The language is where it is, and where it is is &lt;em&gt;everywhere&lt;/em&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
