Date: Tue, 23 May 2006 17:42:51 +0100 From: Alex Zbyslaw <xfb52@dial.pipex.com> To: FreeBSD Questions <freebsd-questions@freebsd.org>, Joe Auty <joe@netmusician.org> Subject: Re: Python port problems Message-ID: <44733B8B.6030404@dial.pipex.com> In-Reply-To: <448xoska3k.fsf@be-well.ilk.org> References: <9842C36E-C450-4282-9019-BA2DD3476684@netmusician.org> <fb6605670605221727h719579a2gdeae84452036f6e8@mail.gmail.com> <2A55FF5E-F764-406A-BE0E-272246F425B5@netmusician.org> <448xoska3k.fsf@be-well.ilk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Lowell Gilbert wrote: >Joe Auty <joe@netmusician.org> writes: > > >> >>$ python -c 'import sys; print sys.path' >>['', '/usr/local/lib/python24.zip', '/usr/local/lib/python2.4', '/usr/ >>local/lib/python2.4/plat-freebsd5', '/usr/local/lib/python2.4/lib- >>tk', '/usr/local/lib/python2.4/lib-dynload', '/usr/local/lib/ >>python2.4/site-packages'] >> >> >>I don't have a /usr/local/bin/python in there. Is that my problem? >> >> > >That's where the ports would install it, so that does sound like a >problem. Look at "which python" and "pkg_info|grep python". > > The executable /usr/local/bin/python has no business being in the path for *modules*. This is not your problem. I have never used mailman so do not know how it picks up its modules. It *might* install them into one of these directories on the module patch, but more likely it just pushes its own directory of modules onto this path when it runs, in which case the output you have won't help. Have you tried simply re-installing mailman? Maybe you upgraded python at some point after installing mailman and that is throwing something. --Alex
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44733B8B.6030404>