How To: Install PIP In Linux

Today’s article is going to teach you how to install PIP in Linux. PIP is a reverse acronym meaning ‘PIP Installs Packages” and it’s a handy tool for the installation and management of Python applications. This article should be pretty short and easy for anyone to understand. 

This article is going to be pretty basic, merely telling you how to install PIP and not a whole lot more. The reason I write this article is because it needs to be written. I should also point out that Python is a programming language, though I’d expect most visitors to know that already. But, yes, this article needed to be written.

See, I wanted to tell you about a lovely piece of software (or three), but they all need to be installed with PIP. So, rather than write out the long installation instructions for various distros and package managers each time, I figured I’d make a single article that told you how to install PIP.

That’ll save some time and effort. I can refer back to this when those articles are written. There are many Python applications that can be installed with relative ease – just like you’re installing from your regular Linux repositories. PIP’s Python applications can be installed and uninstalled in the terminal while using PIP, so it’s quite easy.

So then, let’s learn how to…

Install PIP In Linux:

Installing PIP requires a terminal. If you don’t know how to open the terminal, you can do so with your keyboard – just press CTRL + ALT + T and your default terminal should open.

Once you have the terminal open, you can install the appropriate PIP. Most folks will be using Python 3, but a smattering of people will still be using Python 2. I will list the installation instructions, where applicable, with Python 2’s instructions first.

Debian/Ubuntu/derivatives:

SUSE/openSUSE/derivatives:

Fedora/derivatives:

RHEL/CentOS/derivatives:

Arch/Manjaro/derivatives:

Slackware:

Read Install PIP For Slackwaare Instructions.

The basic usage of PIP is pip install <package>, pip uninstall <package>, and pip search <package>. My readers are smart enough to understand that without further instructions. You can also learn a lot by using man pip. Now you know how to install PIP in Linux.

Closure:

And there you have it. You have an article telling you how to install PIP in Linux, enabling you to install Python packages/programs quickly and easily inside the Linux terminal. It’s also one more article in my series of articles. I’m now well within a month of when the project is allowed to end and I still have a lot of articles left in me, so I’d expect it to keep going for long into the future. Or at least until someone steps up and takes the site over for me.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your own site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

Smash a button!
[Total: 2 Average: 5]

‘sudo apt remove’ vs ‘sudo apt purge’

Today’s article is going to cover ‘sudo apt remove’ vs ‘sudo apt purge’ and will be a different format than some articles. It’s a brief article meant to answer a specific question. It’s nothing more, and nothing less.

The question would be, “What’s the difference between sudo apt remove and sudo apt purge?” It’s a perfectly fine question, thanks. This article will answer it.

It does open up an idea. If you have any questions, you can always just “Ask KGIII” a question. For example, the question prompting this article might be, “What’s the difference between sudo apt autoremove vs sudo apt purge?” It’s a perfectly legitimate question, and a good example, of the kinds of questions I’d welcome.

So, for fun, we can pretend someone asked this question! 

If you don’t ask me any questions, I may just have to pretend you did and write my own questions and answers all by myself! However, this is the kind of question I’d be looking for. Leave a comment with a question, thanks!

If you lie about your email address to ask a question, that’s fine – just don’t also opt to subscribe to responses. It results in some ‘spammy’ domain behavior and I’d like to avoid that. Use  @example.com, if you want. It should work but there is no example.com of note so bouncing emails won’t be a problem. On the other hand, others can attest to the fact that I’ve sent zero spam messages.

‘sudo apt remove’ vs ‘sudo apt purge’:

In this case, both of these commands are used to remove software from your system. These commands are valid in distros like Debian or Ubuntu, systems that use APT as the package management system. If you want to remove software, the commands would look like one of the following:

With both of these commands, you’ll remove software. It will not only remove the software, it’ll mark the software as uninstalled in your database of installed applications. This means you can opt to install the software again.

But, there is a difference. When you use sudo apt remove <package_name>, you just remove the software itself. When you use sudo apt purge <package_name>, it not only removes the package, it also removes the configuration files.

In theory, you can do ‘apt remove’ and then re-install the application at a later date while keeping the pre-existing, pre-removal configuration. The regular ‘apt remove’ doesn’t touch configuration files, it only removes those things that were listed as files in the packages manifest and created during the installation process.

So, when you run ‘apt remove’ you’re removing it from your system. When you run ‘apt purge’ you’re making sure (ideally) no traces of it remain. I say “ideally” because it’s not as cut and dry as one might think. Package management isn’t all that smart and things like MySQL will leave behind a user, and other package installs will do similar. 

As a bonus, if you’ve seriously messed up an application’s configuration then you can purge it and have a clean slate, with (ideally) no previous configuration files left over. Of course, if you just use ‘apt remove’ then your configuration files may still exist. If you want to maybe install the application again, and you were happy with the say it was configured, you should use ‘apt remove’. Otherwise, use ‘apt purge’.

If you, like me, are curious as to how the purge command really works (it’s not all that intelligent) then click here to learn how the purge command works. The answer is well-written and, more importantly, is correct (inasmuch as I understand). It’s well worth reading, for a better understanding. As I mentioned elsewhere, the package manager isn’t really all that intelligent – but it is what it is and it’s much easier than doing it all yourself!

Closure:

And there you have it. You have another article! This one is kinda like a pretend person asked a question and I answered the question in the form of an article. I’d like to do that sort of thing every couple of weeks, but it’d require someone to actually ask me questions.

I don’t mind if they’re questions I have to research. I think it’d be an interesting new aspect to the site. We can call it ‘Reader Questions’ and maybe give out a prize of some type if your question is chosen. I mean, you shouldn’t need a prize but it might motivate a few of you. Leave a ‘Reader Question’ as a comment on this post and we’ll see how it goes! If it looks like it might work, I’ll add it as a new category.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your own site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

Smash a button!
[Total: 5 Average: 5]
Linux Tips
Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.
Zoom to top!