See issue31 for the sequel to this bug.

Fixed.

rev2565 (branches/v2)
rev2566 (trunk)

Note:  This issue does not apply to Exchanger, since Exchanger is currently pure
Python... the Exchanger extension module is (mis?)placed under CitcomS.

This is an issue discovered with Pythia on Pangu: when 'pkgpyexecdir' is
distinct from 'pkgpythondir' (on Pangu, these are
/usr/lib64/python2.3/site-packages and /usr/lib/python2.3/site-packages,
repectively), the .so extension modules are divorced from their associated .py
files.  The .py files are installed under 'pkgpythondir', and the .so files are
installed under 'pkgpyexecdir'... this simple-minded approach doesn't work
because Python's module search path works in the straitforward way one would
expect:  it finds the .py files under /usr/lib, but not the orphaned .so files
under /usr/lib64.

After much thought, I decided that the rule is this:  if a Python package
contains any native modules, then the entire package -- including
platform-independent .py files -- must be installed under the
architecture-dependent 'pkgpyexecdir'.