easy-install | 易学教程

easy_install.exe Permission Denied on Windows 8

阅读更多关于 easy_install.exe Permission Denied on Windows 8

问题 Running command prompt as an administrator I try to run: easy_install -U setuptools It returns the following: Searching for setuptools Reading https://pypi.python.org/simple/setuptools/ Reading http://peak.telecommunity.com/snapshots/ Reading https://pypi.python.org/pypi/setuptools Best match: setuptools 0.8 Processing setuptools-0.8-py2.7.egg setuptools 0.8 is already the active version in easy-install.pth Installing easy_install-script.py script to C:\Python27\Scripts Installing easy

Upgraded Python on Snowleopard Using Homebrew now pip and easy_install don't work

阅读更多关于 Upgraded Python on Snowleopard Using Homebrew now pip and easy_install don't work

问题 I am new to python, I have changed my path to point to the new python 2.7, but pip and easy_install, and mercurial are still looking at the default installed version 2.6. How do I fix this? 回答1: You have to re-install easy_install using Python 2.7 and all other modules as well. Don't expect that existing packages installed with a different interpreter are supposed to work out of the box with a new interpreter. Reinstalling into the new Python 2.7 interpreter is the way to go. First step:

How to install python-ldap on a python 2.7 virtualenv on windows without compiling

阅读更多关于 How to install python-ldap on a python 2.7 virtualenv on windows without compiling

问题 I am using Windows as my main python 2.7 development environment and I want to install python-ldap on a virtual environment. The python-ldap package needs compiling :( and of course I can't compile it in my environment. So I tried finding binaries in order to install them in my virtual environment through easy_install (FYI you can do easy_install package.exe and the package will be installed). I found the distributed binaries here: https://pypi.python.org/pypi/python-ldap/ Unfortunately, they

Installing pip using easy_install

阅读更多关于 Installing pip using easy_install

I don't have root access and i want to install python from scratch. So I downloaded the python source code and compiled it. Next I wanted to install pip . But when I ran python get-pip.py I got this error: ImportError: cannot import name HTTPSHandler Not having root access then I couldn't install stuff needed. So I thought maybe I can install pip with easy_install so I went and installed setuptools which has easy_install . But when I run easy_install pip I get this error: Searching for pip Reading https://pypi.python.org/simple/pip/ Download error on https://pypi.python.org/simple/pip/:

easy_install or pip as a limited user?

阅读更多关于 easy_install or pip as a limited user?

问题 Standard python distutils provides a '--user' option which lets me install a package as a limited user, like this: python setup.py install --user Is there an equivalent for easy_install and pip ? 回答1: For pip , see User Installs for details, but basically, it's just what you'd expect: pip install --user Foo It's a bit trickier for easy_install . As Ned Deily points out, if you can rely on distribute rather than setuptools , and 0.6.11 or later, you can just use --user the same as pip . But if

How can I make setuptools install a package from another source that's also available on pypi with the same version number?

阅读更多关于 How can I make setuptools install a package from another source that's also available on pypi with the same version number?

It's a similar question to How can I make setuptools install a package that's not on PyPI? but not the same. As I would like to use the forked version of some package, setuptools ignore the dependency link (as it has the same version number). Is there a way to force using the link from the dependency_links? Or is the only way to change the version number in the forked repo? requires = [ ... 'pyScss==1.1.3' ... dependencies = [ 'https://github.com/nadavshatz/pyScss/zipball/master#egg=pyScss-1.1.3' ] Update Weird, apparently it works if this package is the only one in the required list, that is

Including global package into a virtualenv that has been created with --no-site-packages

阅读更多关于 Including global package into a virtualenv that has been created with --no-site-packages

I'd usually prefer to create virtualenvs with --no-site-packages option for more isolation, and also because default python global packages includes quite a lot of packages, and usually most of them are not needed. However I'd still want to keep a few select packages in global, like PIL or psycopg2. Is there a good way to include them into the virtualenv, that can also be automated easily? If you're using virtualenvwrapper and you might be able to use the postmkvirtualenv script to automatically create symlinks in the new virtualenv sitepackages directory. #!/bin/sh cdsitepackages ln -s /path

easy_install lxml on Python 2.7 on Windows

阅读更多关于 easy_install lxml on Python 2.7 on Windows

问题 I'm using python 2.7 on Windows. How come the following error occurs when I try to install [lxml][1] using [setuptools][2]'s easy_install? C:\>easy_install lxml Searching for lxml Reading http://pypi.python.org/simple/lxml/ Reading http://codespeak.net/lxml Best match: lxml 2.3.3 Downloading http://lxml.de/files/lxml-2.3.3.tgz Processing lxml-2.3.3.tgz Running lxml-2.3.3\setup.py -q bdist_egg --dist-dir c:\users\my_user\appdata\local\temp\easy_install-mtrdj2\lxml-2.3.3\egg-dist-tmp-tq8rx4

Python - package installed with easy_install is not being detected (PIL 1.1.7)

阅读更多关于 Python - package installed with easy_install is not being detected (PIL 1.1.7)

问题 I installed PIL with easy_install but for some reason when I run a file that uses it, I get: ImportError: No module named PIL Does anyone know why this could be? I think it's also worth mentioning that I installed web.py through easy_install and it's working fine. 回答1: I have the same problem. To me, it looks like a bug in PIL easy_install process. The library is installed, but you have to leave out PIL from imports (aka import Image works), which is obviously wrong. To solve, don't use easy

Eggs in path before PYTHONPATH environment variable

阅读更多关于 Eggs in path before PYTHONPATH environment variable

If I have packages installed from easy_install , the eggs are prepended to sys.path before the items in the PYTHONPATH variable. For example, if I have an egg package called foo installed as well as a package called foo in the current directory, and then do this: PYTHONPATH="." python >>> import foo This will use the egg version of foo instead of the local directory. Inspecting sys.path shows that eggs are placed before items from PYTHONPATH . This seems broken. Is there any way to override this behavior? Unfortunately this is done with a hard-coded template deep inside setuptools/command/easy