Here's a goofy little sample to demonstrate that dynamic module loading
works under BeOS.

It also demonstrates a little quirk in the Advanced Access DR9 release... if
you load an add-on with the full path of the add-on (like Python will try to
do), the current working directory must be where the binary lives (in this
case, the python interpreter).

This is cheesy, and means two things:

1) if you build a module in your current directory, and try to load it
   into Python, it will fail

2) the dynamic import code has a silly hack in it to change to the directory
   where Python is installed, load the add-on module, then change back to
   the current directory

- Chris Herborth (chrish@qnx.com)
  June 1, 1997
