Unable to locate package python termux ошибка

The apt-get pip installation error “Unable to locate package python-pip” can occur if your apt repositories are out of date, or if your system uses python3-pip or python2-pip packages instead. You may already have it – check to see if the pip2 or pip3 commands are available.

The other day I was toying around with an older version of Ubuntu. Or, rather, I was stuck using an older version of Ubuntu for reasons I’d rather forget. When trying to install some Python package via pip install <whatever>, I got:

“Hmm, weird” I thought. I could have sworn it was already installed. But, I’ve been in this situation a million times before. I know exactly what to do!

Then I did the next logical thing, and tried running:

sudo apt-get install python-pip

But, unfortunately, that didn’t do what I thought it was going to do. Instead, I was greeted with the following error message:

Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package python-pip

What. That always used to work!

Fortunately, I was able to figure it out. Let’s look at a few different ways you can install pip – one of these will work!

Fix 1: You might already have it!

If you’re not able to run the pip command, it’s possible your system already has it installed as pip2 or pip3 instead. Newer versions of Debian based systems like Ubuntu 20.04 will install Python 2 as “python2” and Python 3 as “python3”. I really look forward to the day when this isn’t the case. Literally nobody should be using Python 2 anymore. It’s been long enough.

Anyway, try the following if you must use Python 2 and need pip as well:

pip2 install <your package>

Or, if you’re really trying to get pip for Python 3, try this:

pip3 install <your package>

Still didn’t work? Alright, well, moving on then…

Fix 2: Try installing python2-pip or python3-pip instead

The next logical step, if pip2 or pip3 didn’t work, is to try installing those. You can short-circuit the guesswork if you can figure out if you have the python2 or python3 commands. Depending on which version of Python you actually want, that is.

If you have one of those, good news! One of the following commands should work.

If you want Python 2 pip, run this:

sudo apt-get install python2-pip

And if you want Python 3 pip, try this one:

sudo apt-get install python3-pip

Still nothing?? Well, don’t worry. I have a few more tricks up my sleeve.

Fix 3: Update your apt repositories

You might just need to update your apt repositories. Unlikely, yes, but still possible. python2-pip or python3-pip should have already been in your apt packages list on install. But, maybe you installed your OS without internet access, or maybe you just… did something weird. I don’t know.

It’s worth a try though, right?

Try the following:

sudo apt-get update && sudo apt-get install python-pip

If that didn’t work, try substituting “python-pip” with one of the specific variations, python2-pip or python3-pip. Yes, we’re grasping at straws here.

Fix 4: Add the “universe” repository

If you made it this far wit no luck, we might be in trouble. But, hang in there. We have a couple more things to try.

You might have some success by installing the “universe” repository. Beware though, these are packages from all over the place, not just the Debian or Ubuntu sanctioned ones. We don’t need their rules anyway, right? Please don’t sue me if you break something – you’ve been warned!

sudo apt-get install software-properties-common
sudo apt-add-repository universe
sudo apt-get update
sudo apt-get install python-pip

Again, if you don’t have success trying python-pip, try the python2-pip or python3-pip packages instead.

Fix 5: Use the ensurepip module

Python comes with a built-in way to make sure pip in installed. Though, it’s unlikely to work if you’re on Ubuntu or Debian, because they usually disable it. Or, at least, it’s always disabled when I try this. But it’s worth a shot. I’ve been saying that a lot lately… hopefully you haven’t had to read down this far.

python -m ensurepip --upgrade

You’re more than likely going to get the following error or some variation of it:

ensurepip is disabled in Debian/Ubuntu for the system python.
Python modules for the system python are usually handled by dpkg and apt-get.
    apt install python3-<module name>
Install the python3-pip package to use pip itself.  Using pip together
with the system python might have unexpected results for any system installed
module, so use it on your own risk, or make sure to only use it in virtual
environments.

Rats. Now we’re down to our nuclear option – use the get-pip script.

Fix 6: Use the get-pip.py script

Alright – this is guaranteed to work, but it’s definitely not the best option. Why? Because on Debian and Ubuntu, packages like pip are managed through apt. And if you step outside that package management system, you’re asking for trouble, because now apt doesn’t know what you have installed, and you can’t uninstall or manage dependencies for those packages with apt.

But, if this is an emergency, go ahead and give it a try:

curl https://bootstrap.pypa.io/get-pip.py | python

Or, if you don’t have curl installed and can’t or don’t want to install it, you can use wget instead with the following one-liner:

wget -qO - https://bootstrap.pypa.io/get-pip.py | python2

There you go. Now you should have pip.

You might get the following warning:

WARNING: The scripts pip, pip3 and pip3.9 are installed in '/home/user/.local/bin' which is not on PATH.
Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.

If you do, that means you’ll have to add /home/<you>/.local/bin to your $PATH environment variable. You can do this (if you use bash) by adding the following to the bottom of your .bashrc file:

You’ll have to log out / log back in again for this to take effect. Or open a new terminal window if you’re logged into the desktop environment.

Conclusion

So there you go, one of those was guaranteed to work. Well, I can’t say “guaranteed”, because there’s always something, but I can say “probably”. Yeah, we’ll go with that. One of those probably worked. If you can think of any possible solutions I may have missed please let me know!

Hope this helped, and if it didn’t, good luck.