Distutils extra files

And if the Extension instance has no sources after processing all source generators, no extension module will be built. This is the recommended way to conditionally define extension modules.

The first argument contains the Extension instance that can be useful to access its attributes like depends , sources , etc. The second argument gives a path to a build directory that must be used when creating files to a disk. The file will be removed from the source directory when Python exits. This is the place where one should build temporary files. This facility can be used to maintain very similar code blocks requiring only simple changes between blocks. Two forms of template conversion are supported.

The second form is used for all other cases. All of the repeat rules in a block must contain the same number of comma-separated words indicating the number of times that block should be repeated.

There are two forms for the repeat rule: named and short. A named repeat rule is useful when the same set of repeats must be used several times in a block.

Once a named repeat specification has been introduced, the same repeat rule may be used in the current block by referring only to the name i. Non-Fortran files use a separate syntax for defining template blocks that should be repeated using a variable expansion similar to the named repeat rules of the Fortran-specific repeats. NumPy Distutils preprocesses C source files extension:.

The symbol is used to wrap macro-style variables to empower a string substitution mechanism that might describe for instance a set of data types. These variables are replaced in each repeat block with corresponding word. All named variables in the same repeat block must define the same number of words. The next line is the first line that will be repeated using the named rules. Inside the block to be repeated, the variables that should be expanded are specified as name.

You do have to include the runner script because it has no. I am not sure if it would pick up. I am unsure about how to create multiple packages. The docs are a little too concise and I read too fast. If you include a path, you can control where they go. Making the installation tarball Well, that's the lot.

It's quite simple really, as long as you keep to the pattern. If you want extra folders and sub-packages and so forth, it gets a little hairy. But, I suppose, if you want all that then you will have no trouble extending it from this tutorial. To make the installation tarball, you simply run: python setup. Look for errors. I also try to run 'runner' and see what ensues. You can add your app to it quite easily, I was surprised how quickly this worked.

Requires Python 2. Please consult the Python Docs for this info. Follow the instructions in it to complete registration. If you have an account, obv, choose 1. If you chose 2, you will get an email; read and do. I then re-did the register command, and logged-in via option 1. Not sure if this was needed. After all that, you can quickly find you app in the Cheese Shop via your browser, or sign up for their RSS feed. I have no idea why and not much help seems forthcoming.

I will update when I get a clue. Most Python users will not want to use this module directly, but instead use the cross-version tools maintained by the Python Packaging Authority. In particular, setuptools is an enhanced alternative to distutils that provides:.

The recommended pip installer runs all setup. Refer to the Python Packaging User Guide for more information. For the benefits of packaging tool authors and users seeking a deeper understanding of the details of the current packaging and distribution system, the legacy distutils based user documentation and API reference remain available:.