This argument is only useful if the project will be installed as a zipfile, and there is a need to have all of the listed resources be extracted to the filesystem as a unit. However, if someone is working on a package by checking out with that system, they will need the same plugin s that the original author is using. Leading zeros within a series of digits are also ignored, so 2. This means that after doing code changes you will have to run setup. To verify the authenticity of the download, grab both files and then run this command: gpg --verify Python-3. For more information, see the section below on.
See the section below on the command for more details. However, since it can be tedious to create such files by hand, you may want to create a distutils extension that will create the necessary files from arguments to setup , in much the same way that setuptools does for many of the setup arguments it adds. There are also some options you will probably never need, but which are there because they were copied from similar bdist commands used as an example for creating this one. However, if you are cross-compiling or doing some other unusual things, you might find a use for this option. For a complete description and examples, see the section below on.
This can be useful in circumstances where your installation directory is being shared by code running under multiple platforms e. This option is mainly included for use in testing. Note: this is not a py2exe replacement; the. And, if you want to override for testing purposes, you can just run setup. This deployment is done in such a way that changes to the project source are immediately available in the staging area s , without needing to run a build or install step after each change.
As eggs are deprecated and pip-based installs fall back to the platform-specific location for installing data files, there is no supported facility to reliably retrieve these resources. Knowing these things will also help you correctly specify what versions of other projects your project depends on. You can avoid these hassles by using the saveopts command. This may also be important for your users and contributors if they track intermediate revisions of your project using Subversion; be sure to let them know when you make changes that remove files from inclusion so they can run setup. Following a release number, you can have either a pre-release or post-release tag. So, if you are using a test package that does not support this, we suggest you encourage its developers to implement test suite support, as this is a convenient and standard way to aggregate a collection of tests to be run under a common test harness. This is important in order to make sure that dependency processing tools will know which versions of your project are newer than others.
The globs may include subdirectory names, if the data files are contained in a subdirectory of the package. Then, you can register entry points in your setup script. Or it could be a package that is required to run on a specific operating system. The release managers and binary builders since Python 2. This will allow a project to work on multiple different platforms without installing dependencies that are not required for a platform that is installing the project.
Post-release tags are generally used to separate patch numbers, port numbers, build numbers, revision numbers, or date stamps from the release number. Mac and Windows which have different absolute locations for the code under development, but the same relative locations with respect to the installation directory. These are mappings from command or argument names to a specification of where to import a handler from. Notice that after each pre or post-release tag, you are free to place another release number, followed again by more pre- or post-release tags. Note that this option currently does not uninstall script wrappers! Otherwise, this setting defaults to the location where the distutils would normally install scripts, taking any distutils configuration file settings into account. The entry point should be a function accepting a single directory name, and should yield all the filenames within that directory and any subdirectories thereof that are under revision control. They may be useful for testing and debugging, however, which is why we kept them: --keep-temp, -k Keep the contents of the --bdist-dir tree around after creating the.
Finally, if you are creating builds frequently, and either building them in a downloadable location or are copying them to a distribution server, you should probably also check out the command, which lets you automatically delete all but the N most-recently-modified distributions matching a glob pattern. These options are used by other setuptools commands that modify configuration files, such as the and commands. EasyInstall will recognize this suffix and automatically create a trivial setup. Ordinarily, this is done by having plugin developers include additional files in their ProjectName. This option is included so you can override a default setting in setup. In addition, this keyword is used to support. This lets you browse the standard library the subdirectory Lib and the standard collections of demos Demo and tools Tools that come with it.
See for details and examples of the format of this argument. See the section above for more information. Inclusion and exclusion patterns are package names, optionally including wildcards. That is, if the egg is built for Python 2. Then, a simpler script or cron job could just run setup. Some examples of prerelease tags would include alpha, beta, a, c, dev, and so on. This will do a checkout or a clone, in Git and Mercurial parlance to a temporary folder and run setup.