<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Conda on sugar, spice, &amp;terminal? nice</title>
    <link>https://terminal.space/tag/conda/</link>
    <description>Recent content in Conda on sugar, spice, &amp;terminal? nice</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 09 Jul 2025 15:19:32 +0000</lastBuildDate>
    <atom:link href="https://terminal.space/tag/conda/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why can&#39;t we (pip and conda) be friends?</title>
      <link>https://terminal.space/tech/why-cant-we-pip-and-conda-be-friends/</link>
      <pubDate>Wed, 09 Jul 2025 15:19:32 +0000</pubDate>
      <guid>https://terminal.space/tech/why-cant-we-pip-and-conda-be-friends/</guid>
      <description>&lt;p&gt;&amp;ldquo;Don&amp;rsquo;t mix pip and conda&amp;rdquo; - is the general advice from &lt;a href=&#34;https://www.anaconda.com/blog/using-pip-in-a-conda-environment&#34;&gt;Anaconda&lt;/a&gt;, or if you must, use pip after conda. But why? One of the reasons is that conda and pip have different ways of tracking which packages are installed in an environment, and which packages should be installed in an environment. Let&amp;rsquo;s dig in.&lt;/p&gt;&#xA;&lt;h2 id=&#34;i-just-came-here-for-the-tldr&#34;&gt;I just came here for the TL;DR:&lt;/h2&gt;&#xA;&lt;p&gt;Too bad there isn&amp;rsquo;t a TL;DR. If you&amp;rsquo;d rather run the examples yourself, however, head over to &lt;a href=&#34;https://github.com/intentionally-left-nil/py_dependency_investigation&#34;&gt;https://github.com/intentionally-left-nil/py_dependency_investigation&lt;/a&gt; and follow the instructions. You can run any of the scenarios in the &lt;a href=&#34;https://github.com/intentionally-left-nil/py_dependency_investigation/blob/main/Makefile&#34;&gt;makefile&lt;/a&gt;, and make up your own conclusions&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
