For example, to produce a source distribution, simply invoke: Of course, before you release your project to Py PI, you’ll want to add a bit more information to your setup script to help people find or learn about your project.
And maybe your project will have grown by then to include a few dependencies, and perhaps some data files and scripts: Setuptools can work well with most versioning schemes; there are, however, a few special things to watch out for, in order to ensure that setuptools and Easy Install can always tell what version of your package is newer than another version.
Knowing these things will also help you correctly specify what versions of other projects your project depends on.
A version consists of an alternating series of release numbers and pre-release or post-release tags.
(Note: projects listed in will NOT be automatically installed on the system where the setup script is being run.
They are simply downloaded to the ./directory if they’re not locally available already.
In particular, be sure to read the section on Custom Installation Locations if you are installing anywhere other than Python’s As you can see, it doesn’t take much to use setuptools in a project.
The named class must be instantiable with no arguments, and its instances must support the A list of strings naming resources that should be extracted together, if any of them is needed, or if any C extensions included in the project are imported.files that are generated by your setup script and build process.(And are therefore not in source control or are files that you don’t want to include in your source distribution.)A string or list of strings specifying what other distributions need to be installed when this one is.In addition, this keyword is used to support Automatic Script Creation.A dictionary mapping names of “extras” (optional features of your project) to strings or lists of strings specifying what other distributions must be installed to support those features.