AttributeError: 'module' object has no att

Question

I installed Cygwin with Python set-up tools. When I try to run pip install awscli I get the following error:

$ pip install awscli
Traceback (most recent call last):
  File "/usr/bin/pip", line 8, in <module>
    load_entry_point('pip==1.5.4', 'console_scripts', 'pip')()
  File "build/bdist.linux-i686/egg/pkg_resources.py", line 318, in load_entry_point
  File "build/bdist.linux-i686/egg/pkg_resources.py", line 2221, in load_entry_point
  File "build/bdist.linux-i686/egg/pkg_resources.py", line 1954, in load
  File "/usr/lib/python2.5/site-packages/pip-1.5.4-py2.5.egg/pip/__init__.py", line 9, in <module>
    from pip.log import logger
  File "/usr/lib/python2.5/site-packages/pip-1.5.4-py2.5.egg/pip/log.py", line 9, in <module>
    from pip._vendor import colorama, pkg_resources
  File "/usr/lib/python2.5/site-packages/pip-1.5.4-py2.5.egg/pip/_vendor/pkg_resources.py", line 1112, in <module>
    class MarkerEvaluation(object):
  File "/usr/lib/python2.5/site-packages/pip-1.5.4-py2.5.egg/pip/_vendor/pkg_resources.py", line 1120, in MarkerEvaluation
    'python_implementation': platform.python_implementation,
AttributeError: 'module' object has no attribute 'python_implementation'

Am I missing something in my path or is my Python implementation hosed?

Answer 1

Do you have a folder called "/platform" inside your python app? GOT THE POINT! I remove my own platform.py, it still not work. later i remove the remained platform.pyc ,it worked!

Answer 2

Do you have a folder called "/platform" inside your python app?

If you do, it will scope-shadow the native python "platform" module. When modules you're using try to get information about the system, they'll get a null object back. This will often cause errors like:

AttributeError: 'module' object has no attribute 'version'

AttributeError: 'module' object has no attribute 'machine'

AttributeError: 'module' object has no attribute 'python_implementation'

Simply rename the "/platform" folder to something else to resolve the problem.

Answer 3

I got this error when my .virtualenvs folder for a linux (fedora) system was symlinked to a Network shared drive (on a Windows server). Upgrading the system pip

sudo pip install --upgrade pip

And then creating a new ~/.virtualenvs/ locally with a fresh virtualenv did the trick for me.

Answer 4

Re-installing pip might fix it, try it using easy_install:

sudo easy_install pip