setup.py leaves build, dist, .egg-info etc + even clean doesn't remove them
See original GitHub issueBy default, setup.py leaves build, dist, ${project_name}.egg-info directories in a projects directory.
I’m not convinced these need to be here these days, certainly feels messy to have these.
Putting all this output into one directory would be some improvement. But maybe there’s a better solution ?
python setup.py clean
doesn’t even delete these without adding hacks.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:51
- Comments:17
Top Results From Across the Web
Why does "python setup.py sdist" create unwanted "PROJECT ...
Note that you can have the PROJECT.egg-info artifacts disappear completely from your sdist. The command setup.py egg_info will use the source ...
Read more >Running setuptools commands - Python Packaging Authority
While it is perfectly fine that users write setup.py files to configure a package build (e.g. to specify binary extensions or customize commands), ......
Read more >setuptools.txt
Packages built and distributed using ``setuptools`` look to the user like ordinary Python packages based on the ``distutils``.
Read more >setuptools 3.8.1 - PyPI
Easily download, build, install, upgrade, and uninstall Python packages. ... on PyPI and run setup.py with any supported distutils and Setuptools options.
Read more >Including files in source distributions with MANIFEST.in
After processing the MANIFEST.in file, setuptools removes the build/ directory as well as any directories named RCS , CVS , or .svn from...
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
Rather than trying to clean up files from the source directory, would it be better to be able to do out-of-source package builds? Something like this:
cd /tmp/build && python /path/to/setup.py
. That way those generated files never touch the source directory in the first place.@maphew I suggest that it be added as functionality (it doesn’t work that way currently), then documented as a best practice. It shouldn’t break the way it’s done now.