Description:
The profile script "openoffice.sh" modifies the Python path:

export PYTHONPATH=$PYTHONPATH:/usr/lib/openoffice/basis-link/program/

But when PYTHONPATH is empty, this results in:

:/usr/lib/openoffice/basis-link/program/

That empty entry makes Python always add the current working directory to the path:

~ $ python -c "import os, sys; print os.getcwd() in sys.path"
True
~ $ cd /tmp
/tmp $ python -c "import os, sys; print os.getcwd() in sys.path"
True

This provokes side effects when there's a module in the current working directory whose name conflicts with a module in the standard library:

Traceback (most recent call last):
File "../bin/ipkg-build.py", line 30, in <module>
import itools.gettext
File "/home/herve/Itaapy/LpOD/lib/python2.6/site-packages/itools/gettext/__init__.py", line 22, in <module>
from mo import MOFile
File "/home/herve/Itaapy/LpOD/lib/python2.6/site-packages/itools/gettext/mo.py", line 19, in <module>
from gettext import GNUTranslations
File "/home/herve/Itaapy/LpOD/itools--lpod/gettext/__init__.py", line 22, in <module>
from mo import MOFile
File "/home/herve/Itaapy/LpOD/itools--lpod/gettext/mo.py", line 19, in <module>
from gettext import GNUTranslations
ImportError: cannot import name GNUTranslations

Inside my "gettext" package, I import "gettext" from the standard library, but then it's just trying to import itself again.

If I remove the ":", it works as expected:

$ export PYTHONPATH=/usr/lib/openoffice/basis-link/program/

So my suggestion is not to reuse $PYTHONPATH if not defined.

Additional info:
* package version(s)

3.2.0-3