Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

egg option does not honour --no-deps #1037

Closed
k4ml opened this issue Jul 10, 2013 · 1 comment
Closed

egg option does not honour --no-deps #1037

k4ml opened this issue Jul 10, 2013 · 1 comment
Labels
auto-locked Outdated issues that have been locked by automation

Comments

@k4ml
Copy link

k4ml commented Jul 10, 2013

If I install package using --egg option with --no-deps, all dependencies still being installed. For example, Fabric require pycrypto and paramiko.

pip install --no-deps Fabric
Downloading/unpacking Fabric
  Running setup.py egg_info for package Fabric

    warning: no previously-included files matching '*' found under directory 'docs/_build'
    warning: no previously-included files matching '*.pyc' found under directory 'tests'
    warning: no previously-included files matching '*.pyo' found under directory 'tests'
Installing collected packages: Fabric
  Running setup.py install for Fabric

    warning: no previously-included files matching '*' found under directory 'docs/_build'
    warning: no previously-included files matching '*.pyc' found under directory 'tests'
    warning: no previously-included files matching '*.pyo' found under directory 'tests'
    Installing fab script to /home/kamal/python/test_pip/.env/bin

Using --egg option:-

./bin/pip install --no-deps --egg Fabric
Downloading/unpacking Fabric
  Using download cache from /home/kamal/.pip/cache/https%3A%2F%2Fpypi.python.org%2Fpackages%2Fsource%2FF%2FFabric%2FFabric-1.6.1.tar.gz
  Running setup.py egg_info for package Fabric

    warning: no previously-included files matching '*' found under directory 'docs/_build'
    warning: no previously-included files matching '*.pyc' found under directory 'tests'
    warning: no previously-included files matching '*.pyo' found under directory 'tests'
Installing collected packages: Fabric
  Running setup.py install for Fabric

    warning: no previously-included files matching '*' found under directory 'docs/_build'
    warning: no previously-included files matching '*.pyc' found under directory 'tests'
    warning: no previously-included files matching '*.pyo' found under directory 'tests'
    installing library code to build/bdist.linux-i686/egg
    zip_safe flag not set; analyzing archive contents...
    fabric.version: module references __file__
    removing 'build/bdist.linux-i686/egg' (and everything under it)
    Processing Fabric-1.6.1-py2.7.egg
    Extracting Fabric-1.6.1-py2.7.egg to /home/kamal/python/test_pip/.env/lib/python2.7/site-packages
    Adding Fabric 1.6.1 to easy-install.pth file
    Installing fab script to /home/kamal/python/test_pip/.env/bin

    Installed /home/kamal/python/test_pip/.env/lib/python2.7/site-packages/Fabric-1.6.1-py2.7.egg
    Processing dependencies for Fabric==1.6.1
    Searching for paramiko>=1.10.0
    Reading https://pypi.python.org/simple/paramiko/
    Best match: paramiko 1.10.1
    Downloading https://pypi.python.org/packages/source/p/paramiko/paramiko-1.10.1.tar.gz#md5=4ba105e2d8535496fd633889396b20b7

After digging further, this is turn out to be setuptools behavior. If invoked with --single-version-externally-managed as in pip default behavior, only the package get installed, leaving up to pip to manage the dependencies. I can't find any option to disable dependencies tracking when invoking setuptools without --single-version-externally-managed. Anyone has any idea or I'm on a dead end now ?

@dstufft
Copy link
Member

dstufft commented Mar 28, 2014

This issue is quite old, but it's unfortunately not something pip can really fix. --egg bypasses pip's normal dependency solver.

@dstufft dstufft closed this as completed Mar 28, 2014
@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 5, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation
Projects
None yet
Development

No branches or pull requests

2 participants