Background
I'm working on an academic project to (basically) analyze some "who follows whom" graphs and wanted to get some real data (by building some small datasets) from Twitter using one of the Python Twitter API packages in order to test some ideas I have.
I was a bit careless and installed two packages:
a) python-twitter0.8.2
(http://pypi.python.org/pypi/python-twitter/0.8.2)
b) twitter1.9.1
(http://pypi.python.org/pypi/twitter/1.9.1)
(a) is called python-twitter
in pypi, and (b) is called twitter
, so that's how I'll refer to them.
Both of these are called by import twitter
in the Python interpreter, but when I write that line, I always get the twitter
one (if I can figure out how to use the python-twitter
one, I'll be able to proceed, but will still have the same underlying problem).
Problem
Since I don't need the twitter
package, I decided to uninstall it with pip:
$ sudo pip uninstall twitter
which gives the output:
Uninstalling twitter:
Proceed (y/n)? y
Successfully uninstalled twitter
(actually, I tried the same thing with python-twitter
and got a similar response).
However, when running pip freeze
, both of these packages show up on the installed list! In fact, I can still use the import twitter
command successfully in the interpreter. Clearly the packages have not been uninstalled. What I would love to know is how to uninstall them!
Other Info
I'm using Python 2.7 and Ubuntu 12.04
When running IDLE instead of the shell interpreter, and I type help('modules')
, neither twitter
nor python-twitter
shows up in the list. When typing help('modules')
into the shell interpreter, I get a segmentation fault error, and the interpreter crashes. Here's the error:
>>> help('modules')
Please wait a moment while I gather a list of all available modules...
/usr/lib/python2.7/dist-packages/gobject/constants.py:24: Warning:
g_boxed_type_register_static: assertion `g_type_from_name (name) == 0' failed
import gobject._gobject
/usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:40: Warning:
g_boxed_type_register_static: assertion `g_type_from_name (name) == 0' failed
from gtk import _gtk
** (python:2484): CRITICAL **: pyg_register_boxed: assertion `boxed_type != 0' failed
/usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:40: Warning: cannot register
existing type `GdkDevice'
from gtk import _gtk
/usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:40: Warning: g_type_get_qdata:
assertion `node != NULL' failed
from gtk import _gtk
Segmentation fault (core dumped)
Why other questions have not resolved this for me:
I looked at the similar post at pip freeze lists uninstalled packages and am not having the same issues.
$ sudo which pip
/usr/bin/pip
$ which pip
/usr/bin/pip
which is the same output. In addition, $ sudo pip freeze
gives the same output as $ pip freeze
.
Any help is very much appreciated!
You can always manually delete the packages; you can run:
to remove that package from your
dist-packages
directory. You may have to edit theeasy-install.pth
file in the same directory and remove thetwitter
entry from it.For me, it was due to the fact that I was running
pip freeze
, which gave me different results thansudo pip freeze
.Since I was uninstalling using
sudo
, it was not uninstalling it in the "non-sudo
" session. Uninstalling withoutsudo
fixed that.I was facing difficulty while upgrading a package because pip was not able to uninstall it successfully. I had to delete the .egg-info and the folder as well in /usr/lib/python2.7/dist-packages and then I tried to install with --upgrade and it worked.
While Martin's solution works, as a work around, it does not provide a direct answer. Ubuntu's pip version for your Ubuntu version (12.04) is:
This is also the same version for Debian Wheezy. This version has a weired bug, which causes packages not to be removed.
If you obtain pip from upstream using the script
get-pip.py
you will have a fixed version of pip which can remove pacakges (as of now v. 1.5.6).update
Python's pip is really a fast moving target. So using Debian's or Ubuntu's pip is guaranteed to have bugs. Please don't use those distribution's
pip
. Instead install pip from upstream.If you would like to register pip installed packages as system packages I really recommend that you also use stdeb.
In my case (moving pyusb 0.4x to 1.0x), removing the old package with apt-get remove python-usb and manually installing the manually downloaded package via python setup.py worked. Not pretty, but working.