Re: Bug#178373: debconf: severity critical

[Graham Wilson <bob@decoy.wox.org>]

On Fri, Jan 31, 2003 at 02:46:00PM +1100, Donovan Baarda wrote:
> On Fri, 2003-01-31 at 09:59, Josselin Mouette wrote:
> > Le jeu 30/01/2003 ? 22:42, Bernhard Kuemel a ?crit :
> [...]
> > > ImportError: /usr/local/lib/python2.2/lib-dynload/math.so: undefined
> >                ^^^^^^^^^^^^^^^^^^^^^^^^
> > > symbol: PyFPE_jbuf
> > 
> > The issue isn't in mailman. You have some python2.2 binaries in your
> > /usr/local tree, that's why some things started to fail at the very
> > beginning.
> 
> How is it that the /usr/local/ modules were even being imported? I
> thought there was a big discussion about using "#!/usr/bin/python" 
> instead of "#!/usr/bin/env python" to avoid exactly this problem.

probably becuase there are /usr/local/ dirs in python module import
path:

 $ python
 Python 2.2.2 (#1, Jan 18 2003, 10:18:59)
 [GCC 3.2.2 20030109 (Debian prerelease)] on linux2
 Type "help", "copyright", "credits" or "license" for more information.
 >>> import sys
 >>> sys.path
 ['', '/usr/lib/python2.2', '/usr/lib/python2.2/plat-linux2',
 '/usr/lib/python2.2/lib-tk', '/usr/lib/python2.2/lib-dynload',
 '/usr/local/lib/python2.2/site-packages',
 '/usr/lib/python2.2/site-packages',
 '/usr/lib/python2.2/site-packages/Numeric',
 '/usr/lib/python2.2/site-packages/PIL', '/usr/lib/site-python']
 >>>

-- 
gram