![]() You distribute or package many Python module distributions, you might want to Tedious and error-prone, so it’s usually best to put them in the setupĬonfiguration file, setup.cfg-see section Writing the Setup Configuration File. Obviously, supplying even a few of these options on the command-line would be Options to the bdist_rpm command as follows: spec files that don’t haveĬorresponding options in the setup script. spec file are derived from options in the setup script as follows:Īdditionally, there are many options in. Information you supply in the setup script, on the command line, and in anyĭistutils configuration files. To make your life easier, theīdist_rpm command normally creates a. spec file, much as using theĭistutils is driven by the setup script. py bdist_rpm - packager = "John Doe "Ĭreating RPM packages is driven by a. Sdist command, which you can use to select the types of built The bdist command has a -formats option, similar to the Windows, is far more convenient for users even if your distribution doesn’t And creating “smart”īuilt distributions, such as an RPM package or an executable installer for Include extensions that would need to be compiled, it can mean the differenceīetween someone being able to use your extensions or not. Running python setup.py install-but for non-pure distributions, which Obviously, for pure Python distributions, this isn’t any simpler than just Given to the bdist_dumb command the default is to make dumb The filesystem or Python’s prefix directory, depending on the options Installs the Distutils just as though you had downloaded the source distributionĪnd run python setup.py install. tar.gz unpacking this tarball from the right place Thus, the above command on a Unix system createsĭistutils-1.0. Has to be unpacked in a specific location to work.) (That tar file is considered “dumb” because it The defaultįormat for built distributions is a “dumb” tar file on Unix, and a simpleĮxecutable installer on Windows. Then the Distutils builds my module distribution (the Distutils itself in thisĬase), does a “fake” installation (also in the build directory), andĬreates the default type of built distribution for my platform. Uses the setup script and the bdist command family to generate builtĪs a simple example, if I run the following command in the Distutils source Source distributions and turning them into built distributions for as many Original developer does not or it could be software periodically grabbing new Of course, the module developer could be their own packager or the packager couldīe a volunteer “out there” somewhere who has access to a platform which the ![]() Into built distributions for as many platforms as there are packagers. Intermediary species called packagers springs up to turn source distributions Specialty-writing code and creating source distributions-while an Obviously, no one person will beĪble to create built distributions for every platform under the sun, so theĭistutils are designed to enable module developers to concentrate on their Users, it’s a Debian package and so forth. ![]() RPM for Windows users, it’s an executable installer for Debian-based Linux Your module distribution: for users of RPM-based Linux systems, it’s a binary (And “installer” is a term specific to the world ofĪ built distribution is how you make life as easy as possible for installers of Necessarily binary, though, because it might contain only Python source codeĪnd/or byte-code and we don’t call it a package, because that word is already “binary package” or an “installer” (depending on your background). Independently covers all of the relevant information currently included here.Ī “built distribution” is what you’re probably used to thinking of either as a This document is being retained solely until the setuptools documentation
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |