Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups | Web Services





	advanced \| search help

Reference

ActivePython 2.4

Python Documentation

3. Python Runtime Services

3.1 sys -- System-specific parameters and functions

3.2 gc -- Garbage Collector interface

3.3 weakref -- Weak references

3.4 fpectl -- Floating point exception control

3.5 atexit -- Exit handlers

3.6 types -- Names for built-in types

3.7 UserDict -- Class wrapper for dictionary objects

3.8 UserList -- Class wrapper for list objects

3.9 UserString -- Class wrapper for string objects

3.10 operator -- Standard operators as functions.

3.11 inspect -- Inspect live objects

3.12 traceback -- Print or retrieve a stack traceback

3.13 linecache -- Random access to text lines

3.14 pickle -- Python object serialization

3.15 cPickle -- A faster pickle

3.16 copy reg -- Register pickle support functions

3.17 shelve -- Python object persistence

3.18 copy -- Shallow and deep copy operations

3.19 marshal -- Internal Python object serialization

3.20 warnings -- Warning control

3.21 imp -- Access the import internals

3.22 zipimport -- Import modules from Zip archives

3.23 pkgutil -- Package extension utility

3.24 modulefinder -- Find modules used by a script

3.25 code -- Interpreter base classes

3.26 codeop -- Compile Python code

3.27 pprint -- Data pretty printer

3.28 repr -- Alternate repr() implementation

3.29 new -- Creation of runtime internal objects

3.30 site -- Site-specific configuration hook

3.31 user -- User-specific configuration hook

3.32 builtin -- Built-in objects

3.33 main -- Top-level script environment

3.34 future -- Future statement definitions

Distributing Python Modules

2. Writing the Setup Script

2.5 Installing Package Data

MyASPN >> Reference >> ActivePython 2.4 >> Python Documentation >> 3. Python Runtime Services >> 3.1 sys -- System-specific parameters and functions

ActivePython 2.4 documentation

2.5 Installing Package Data

Often, additional files need to be installed into a package. These files are often data that's closely related to the package's implementation, or text files containing documentation that might be of interest to programmers using the package. These files are called package data.

Package data can be added to packages using the package_data keyword argument to the setup() function. The value must be a mapping from package name to a list of relative path names that should be copied into the package. The paths are interpreted as relative to the directory containing the package (information from the package_dir mapping is used if appropriate); that is, the files are expected to be part of the package in the source directories. They may contain glob patterns as well.

The path names may contain directory portions; any necessary directories will be created in the installation.

For example, if a package should contain a subdirectory with several data files, the files can be arranged like this in the source tree:

setup.py
src/
    mypkg/
        __init__.py
        module.py
        data/
            tables.dat
            spoons.dat
            forks.dat

The corresponding call to setup() might be:

setup(...,
      packages=['mypkg'],
      package_dir={'mypkg': 'src/mypkg'},
      package_data={'mypkg': ['data/*.dat']},
      )

New in version 2.4.

See About this document... for information on suggesting changes.

Privacy Policy | Email Opt-out | Feedback | Syndication
© ActiveState 2004 All rights reserved