Skip to main content

Making clean more useful.

Project description

Version Downloads Status License

Extends the clean command to remove stuff generated by the development process.

Wait… Why? What??

So clean is useful for developers of C extensions or anything else that takes advantage of the build command. Pure Python packages generate their own set of artifacts that clutter up the source tree. This package extends the clean command so that it removes the following artifacts as well:

  • The distribution directory as generated by the sdist and bdist* commands

  • Top-level .egg-info and .egg directories that creates

  • Local virtual environment directories

  • __pycache__ directories

I come from a C/C++ background where the Makefile usually provide house keeping targets such as clean, dist-clean, and maintainer-clean. This extension is inspired by the same desire for a clean working environment.


The setuptools package contains a number of interesting ways in which it can be extended. The simplest way to use this extension is to install it into the environment and use it. The package extends the clean command by installing a distutils extension:

$ pip install -q 'setupext-janitor'
$ ./ clean --dist --eggs
running clean
removing './my_package.egg-info' (and everything under it)
removing 'dist' (and everything under it)

You can also install the command from within your using the setup_requires and cmdclass keyword parameters to the setup function call. This is a little more difficult than it should be since the setupext_janitor package needs to be imported into so that it can be passed as a keyword parameter before it is downloaded. The easiest way to do this is to catch the ImportError that happens if it is not already downloaded:

import setuptools
   from setupext_janitor import janitor
   CleanCommand = janitor.CleanCommand
except ImportError:
   CleanCommand = None

cmd_classes = {}
if CleanCommand is not None:
   cmd_classes['clean'] = CleanCommand

   # normal parameters
      # normal parameters, ie. console_scripts[]
      'distutils.commands': [
         ' clean = setupext_janitor.janitor:CleanCommand']

This approach is not recommended since the install_requires keyword will install setupext_janitor into a target environment when installing your package from a source distribution. Not to mention that amount of gynmastics required to safely use it from within,


Once the extension is installed, the clean command will accept a few new command line parameters. clean --build

Removes directories that various build commands produce. clean --dist

Removes directories that the various dist commands produce. clean --eggs

Removes .egg and .egg-info directories. clean --environment

Removes the currently active virtual environment as indicated by the $VIRTUAL_ENV environment variable. The name of the directory can also be specified using the --virtualenv-dir command line option. clean --pycache

Recursively removes directories named __pycache__. clean --all

Remove all of by-products. This is the same as using --dist --egg --environment --pycache.

Where can I get this extension from?






Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

setupext-janitor-1.1.2.tar.gz (11.8 kB view hashes)

Uploaded source

Built Distribution

setupext_janitor-1.1.2-py2.py3-none-any.whl (7.6 kB view hashes)

Uploaded py2 py3

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page