<?xml version="1.0" encoding="utf-8" standalone="yes"?><?xml-stylesheet type="text/xsl" href="/rss.xsl"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Python Developer Tooling Handbook – Pip</title>
    <link>https://pydevtools.com/tags/pip/</link>
    <description>The Python Developer Tooling Handbook is a comprehensive guide to Python development tools including uv, ruff, pytest, mypy, ty, and more.</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Fri, 24 Apr 2026 09:00:00 -0400</lastBuildDate>
    
	  <atom:link href="https://pydevtools.com/tags/pip/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Did pip 26 close the gap with uv?</title>
      <link>https://pydevtools.com/blog/did-pip-26-close-the-gap-with-uv/</link>
      <pubDate>Fri, 24 Apr 2026 09:00:00 -0400</pubDate>
      <author>Tim Hopper</author>
      <guid>https://pydevtools.com/blog/did-pip-26-close-the-gap-with-uv/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://pydevtools.com/handbook/reference/pip/&#34;&gt;pip&lt;/a&gt; 26.0 closed two of &lt;a href=&#34;https://pydevtools.com/handbook/reference/uv/&#34;&gt;uv&lt;/a&gt;&amp;rsquo;s clearest feature gaps in January: &lt;a href=&#34;https://pydevtools.com/handbook/explanation/what-is-pep-723/&#34;&gt;PEP 723&lt;/a&gt; script installs and a datetime-based package filter that mirrors uv&amp;rsquo;s &lt;code&gt;--exclude-newer&lt;/code&gt;. The &lt;a href=&#34;https://news.ycombinator.com/item?id=45751400&#34;target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;October 2025 Hacker News thread&lt;/a&gt; that kept circling back to &amp;ldquo;pip has quietly caught up&amp;rdquo; now reads less contrarian than it did at the time, and the &lt;a href=&#34;https://pydevtools.com/blog/openai-acquires-astral/&#34;&gt;OpenAI acquisition of Astral&lt;/a&gt; in March changes the &amp;ldquo;is this safe to depend on&amp;rdquo; calculus at the same time.&lt;/p&gt;
&lt;h2&gt;Review pip&amp;rsquo;s 2025 to 2026 releases&lt;span class=&#34;hx:absolute hx:-mt-20&#34; id=&#34;review-pips-2025-to-2026-releases&#34;&gt;&lt;/span&gt;
    &lt;a href=&#34;#review-pips-2025-to-2026-releases&#34; class=&#34;subheading-anchor&#34; aria-label=&#34;Permalink for this section&#34;&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Four pip releases have landed since April 2025, and the first three narrowed gaps uv was best known for:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Why Doesn&#39;t the Authoritative Python Packaging Guide Mention the Best Thing that&#39;s Happened to Python Packaging?</title>
      <link>https://pydevtools.com/handbook/explanation/uv-not-in-ppug/</link>
      <pubDate>Thu, 27 Feb 2025 14:56:00 +0000</pubDate>
      <author>Tim Hopper</author>
      <guid>https://pydevtools.com/handbook/explanation/uv-not-in-ppug/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://pydevtools.com/handbook/reference/uv/&#34;&gt;uv&lt;/a&gt; is the most widely adopted new Python tool in years, yet the &lt;a href=&#34;https://pydevtools.com/handbook/reference/python-packaging-user-guide/&#34;&gt;Python Packaging User Guide&lt;/a&gt; (PPUG) makes no mention of it.&lt;/p&gt;
&lt;h2&gt;What does uv replace?&lt;span class=&#34;hx:absolute hx:-mt-20&#34; id=&#34;what-does-uv-replace&#34;&gt;&lt;/span&gt;
    &lt;a href=&#34;#what-does-uv-replace&#34; class=&#34;subheading-anchor&#34; aria-label=&#34;Permalink for this section&#34;&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;uv delivers 10-100x faster package operations than &lt;a href=&#34;https://pydevtools.com/handbook/reference/pip/&#34;&gt;pip&lt;/a&gt; while consolidating functionality previously spread across &lt;a href=&#34;https://pydevtools.com/handbook/reference/pip-tools/&#34;&gt;pip-tools&lt;/a&gt;, &lt;a href=&#34;https://pydevtools.com/handbook/reference/virtualenv/&#34;&gt;virtualenv&lt;/a&gt;, &lt;a href=&#34;https://pydevtools.com/handbook/reference/pyenv/&#34;&gt;pyenv&lt;/a&gt;, and more into a single tool. Since its introduction in early 2024, it has become the default recommendation in many Python teams and communities.&lt;/p&gt;
&lt;h2&gt;Who controls packaging.python.org?&lt;span class=&#34;hx:absolute hx:-mt-20&#34; id=&#34;who-controls-packagingpythonorg&#34;&gt;&lt;/span&gt;
    &lt;a href=&#34;#who-controls-packagingpythonorg&#34; class=&#34;subheading-anchor&#34; aria-label=&#34;Permalink for this section&#34;&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The Python Packaging Authority (PyPA) started in 2011 as a working group focused on maintaining specific packaging tools, particularly pip and virtualenv. Its name suggests broad authority over Python packaging, but its scope has always been narrower.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
