Distribution points not updating
via If your project’s tests need one or more additional packages besides those needed to install it, you can use this option to specify them.It should be a string or list of strings specifying what other distributions need to be present for the package’s tests to run.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.Run that script in your project folder, alongside the Python packages you have developed.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.See the section below on Declaring Dependencies for details and examples of the format of this argument.) before processing the rest of the setup script or commands.This argument is needed if you are using distutils extensions as part of your build process; for example, extensions that process setup() arguments and turn them into EGG-INFO metadata files.
You do not need to use this option if you are using , unless you need to add e.g. Your users don’t need to install or even know about setuptools in order to use them, and you don’t have to include the entire setuptools package in your distributions.By including just a single bootstrap module (a 12K file), your package will automatically download and install Please follow the Easy Install Installation Instructions to install the current stable version of setuptools.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.
Especially since it frees you from having to remember to modify your setup script whenever your project grows additional top-level packages or subpackages.