Of course is one of the major goals of the Distutils. This makes your setup script portable across operating systems, which Whatever is appropriate on your current platform before actually using the Theĭistutils will take care of converting this platform-neutral representation into Should be written using the Unix convention, i.e. Note that any pathnames (files or directories) supplied in the setup script Meta-data, see section Additional meta-data. (so far) two packages an explicit list of every module would be tedious to Important since the Distutils consist of a couple of dozen modules split into Specification of pure Python modules by package, rather than by module. There are only two differences between this and the trivial one-fileĭistribution presented in section A Simple Example: more metadata, and the #!/usr/bin/env python from re import setup setup ( name = 'Distutils', version = '1.0', description = 'Python Distribution Utilities', author = 'Greg Ward', author_email =, url = '', packages =, ) The Distutils’ own setup script, shown here, is used to install (Keep in mind that although theĭistutils are included with Python 1.6 and later, they also have an independentĮxistence so that Python 1.5.2 users can use them to install other moduleĭistributions. Of sections: the Distutils’ own setup script. Here’s a slightly more involved example, which we’ll follow for the next couple Setup(), and most information supplied to the Distutils by the moduleĭeveloper is supplied as keyword arguments to setup(). As we saw in sectionĪ Simple Example above, the setup script consists mainly of a call to To describe your module distribution to the Distutils, so that the variousĬommands that operate on your modules do the right thing. The setup script is the centre of all activity in building, distributing, and Independently covers all of the relevant information currently included here. This document is being retained solely until the setuptools documentation
0 Comments
Leave a Reply. |