`pip install` completely ignores existing source builds and installed dependencies
See original GitHub issueI suspect this has to do with #4619.
I am on the latest master, and now every time I call pip install -v -e .
two things happens:
- These packages keeps being reinstalled despite I already have them in my env: setuptools, wheel, Cython, fastrlock
- All modules are re-cythonized and recompiled from scratch, despite they’ve been built and nothing has changed
I will try to build in a fresh env to see if something is wrong with my current env. But it’s better to be confirmed independently.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:21 (21 by maintainers)
Top Results From Across the Web
Difference between pip install options "ignore-installed" and ...
Show activity on this post. There are two pip install options related to reinstalling the packages, which are --ignore-installed and --force- ...
Read more >pip wheel - pip documentation v22.3.1
Disable isolation when building a modern source distribution. Build dependencies specified by PEP 518 must be already installed if this option is used....
Read more >Installing Python Modules (Legacy version) — Python 3.11.1 ...
Note. This guide only covers the basic tools for building and distributing extensions that are provided as part of this version of Python....
Read more >p4lang/third-party Dockerfile - Docker Hub
Be sure to install python packages and code using # `pip install --user --ignore-installed`. If you absolutely *must* use # `python setup.py install`, ......
Read more >pipenv Documentation - Read the Docs
Generates and checks file hashes for locked dependencies when installing from ... Using $ pipenv run ensures that your installed packages are available...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I skimmed the pip code, seems pip always install requirements from
pyproject.toml
https://github.com/pypa/pip/blob/baaf66f70d84cf3367d5b43fec16762ca9703810/src/pip/_internal/distributions/sdist.py#L61-L64 although requirements fromsetup_requires
are installed only when it is missing in the current environment: https://github.com/pypa/pip/blob/baaf66f70d84cf3367d5b43fec16762ca9703810/src/pip/_internal/distributions/sdist.py#L90-L95There’s a bunch of things conda-build does to configure pip. May be worth trying these. In particular I think
PIP_NO_BUILD_ISOLATION
may be relevant, but the others may be relevant as well