<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: How to Fix &#8220;Command &#8216;pip3&#8217; not found&#8221; Error in Linux	</title>
	<atom:link href="https://www.tecmint.com/pip-command-not-found/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.tecmint.com/pip-command-not-found/</link>
	<description>Tecmint - Linux Howtos, Tutorials, Guides, News, Tips and Tricks.</description>
	<lastBuildDate>Thu, 13 Jul 2023 20:14:50 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Lohmar Ashar		</title>
		<link>https://www.tecmint.com/pip-command-not-found/comment-page-1/#comment-2003259</link>

		<dc:creator><![CDATA[Lohmar Ashar]]></dc:creator>
		<pubDate>Fri, 28 Apr 2023 08:20:36 +0000</pubDate>
		<guid isPermaLink="false">https://www.tecmint.com/?p=50553#comment-2003259</guid>

					<description><![CDATA[Hi,

At least some time ago it was not advisable to install &lt;strong&gt;pip&lt;/strong&gt; from the distro&#039;s repo because very often it was an outdated version and, most important, it was not advisable to upgrade it using pip because it was using some different paths. 

At least that was the case with some &lt;strong&gt;Debian&lt;/strong&gt; and or &lt;strong&gt;Ubuntu&lt;/strong&gt; (older) versions. Maybe things changed with the &lt;strong&gt;pip3&lt;/strong&gt; and/or newer versions of &lt;strong&gt;python-pip&lt;/strong&gt; packages.]]></description>
			<content:encoded><![CDATA[<p>Hi,</p>
<p>At least some time ago it was not advisable to install <strong>pip</strong> from the distro&#8217;s repo because very often it was an outdated version and, most important, it was not advisable to upgrade it using pip because it was using some different paths. </p>
<p>At least that was the case with some <strong>Debian</strong> and or <strong>Ubuntu</strong> (older) versions. Maybe things changed with the <strong>pip3</strong> and/or newer versions of <strong>python-pip</strong> packages.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
