pip-wheel-metadata configurable
See original GitHub issueAt the moment pip generates a pip-wheel-metadata
folder right alongside the setup.py. Can we move this to some other temporary folder via some flag/environment variable to not pollute the project source directory once someone does a pip install .
? Thanks!
Issue Analytics
- State:
- Created 5 years ago
- Reactions:10
- Comments:20 (11 by maintainers)
Top Results From Across the Web
pip wheel - pip documentation v22.3.1
Build Wheel archives for your requirements and dependencies. Wheel is a built-package format, and offers the advantage of not recompiling your software during ......
Read more >Core metadata specifications - Python Packaging User Guide
The standard file format for metadata (including in wheels and installed projects) is based on the format of email headers. However, email formats...
Read more >How do you add additional files to a wheel? - Stack Overflow
I created two new virtual environments, both with Python 2.7.5, and installed each package ( pip install multigtfs-0.4.2.tar.gz ). The two environments are ......
Read more >wheel Documentation - Read the Docs
This library is the reference implementation of the Python wheel ... in the [metadata] section of the project's setup. cfg. For example:.
Read more >What Are Python Wheels and Why Should You Care?
If you've installed a Python package using pip , then chances are that a wheel has made the installation faster and more efficient....
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
Speaking to @pfmoore last point, the feels like something where we don’t need a configuration knob. Unless I’m mistaken, this directory doesn’t need to persist between invocations of pip, so why not just always put it in a temporary location instead of pooping it into the current directory?
Hi everybody. It looks not so critical maybe, but IMO it is still quite a big issue because it affects many users. What is the stopper here?
Also, is it technically possible to add the check in tests that pip would never behave in such undesirable way again? I mean that it shouldn’t place any its utility files in the project working space (excluding the build/dist/*.egg-info and “hidden” directories). How such behavior/regression tests could look like?