garyo edited this page Dec 13, 2014 · 1 revision


This page is currently under construction.


This section will outline some ways in which I see a system for building Python packages being used. I'll use NumPy for some of the examples, since this is a good example of a project with a large body of C and Fortran code. The NumPy developers had to write lots of extra code to get their package to build across many platforms with many configurations.

New User

  1. The user goes to the NumPy download page.
  2. The user chooses the binary package (.rpm, .dmg, .egg, .exe) of the latest release for his platform and CPU type.
  3. The user installs the binary package.
  4. import numpy works.

Bug Reporter

  1. The user finds a bug in NumPy and reports it to the developers.
  2. The bug is fixed in SVN.
  3. The user is asked to verify the bugfix.
  4. The user checks out the latest revision from SVN.
  5. python setup.py installl
  6. import numpy works and the user verifies the bugfix. In this case, the user isn't interested in building the package with optimized libraries or a specific compiler. He simply wants to build it using whatever tools are available on his system. For some packages, he might have to install some third party libraries in default locations prior to building.

Experienced User

  1. The user has purchased the Intel Matrix Kernel Library for Windows or downloaded the free version for Linux.
  2. The user checks out the latest revision of NumPy from SVN.
  3. python setup.py build --with-mkl install
  4. The user uses his optimized version of NumPy. In this case, recompiling NumPy with MKL was anticipated by the developers and they were able to add useful default library paths and other details to the setup script.

Existing Tools



Things to think about

Which Python versions will be supported? SCons supports many old versions, but setuptools only supports 2.3 and 2.4. I think that support for 2.3 and 2.4 might be enough. Other projects such as NumPy only support 2.3 and 2.4.


Feel free to add comments in this section.

  • While distutils is a good example to look for inspiration, I think this task should not exclusively focus on packaging Python modules, but be useful for packaging software in general. Thus it is important to capture requirements not only from python conventions but other packaging conventions such as the relevant sections from the GNU Coding Standard. On a design-related note, I believe it would be best to work on a layered approach, where the lower layer provides 'builders' that hook up common packaging tools (rpm, deb, wininst, tar), and a layer that is largely orthogonal to SCons, and thus can be provided on top of it, which encapsulates the actual workflow. Users will thus be able to wire the low-level builders up manually, without necessarily following any standard (install prefixes, etc.), while typical users will use the high level layer, which works out-of-the-box on all platforms, but doesn't provide flexibility advanced users may desire. --StefanSeefeld

Random Code

import distutils.sysconfig
self['PYEXTPREFIX'] = ''
self['PYEXTSUFFIX'] = distutils.sysconfig.get_config_vars('SO')
def PythonExtensionBuilder(*args, **kw):
    kw.setdefault('SHLIBPREFIX', '$PYEXTPREFIX')
    kw.setdefault('SHLIBSUFFIX', '$PYEXTSUFFIX')
    # ...[0] returns only the dynamic library
    return self['BUILDERS']['SharedLibrary'](*args, **kw)[0]
self['BUILDERS']['PythonExtension'] = PythonExtensionBuilder 
Clone this wiki locally
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.