python import sys.path

[John Machin]

On Dec 31, 5:05 am, "Kelly, Brian" <Brian.Ke... at uwsp.edu> wrote:
> I have both 2.4 and 2.5 interpreters installed on a linux box. The
> PythonPath is set to :
>
> PYTHONPATH=/usr/lib64/portage/pym:/prod/bacula/local/lib64/python2.4/site-pa
> ckages:/prod/bacula/local/lib/python2.4/site-packages
>
> My main script is getting called like so:
>
> python2.4 cleanup.py wrkstnbs
>
> The imports statements in cleanup.py are as follows:
>
> import os,sys
> print sys.path
> from datetime import datetime
> from optparse import OptionParser        # used for parsing parameters
> from bacula_conf import *                # used for connecting to our
> databases, etc.
> from registration_cleanup \
>     import RegistrationCleanup           # used for interacting w/
> registration db (sql1)
>                                          # and configuration database
> (genunix)
> import directory_cleanup as fclean       # file cleanup.
>
> One of the scripts being imported from bacula_conf is called
> purge_client.py.
>
> It has the following imports:
>
> import sys
> import MySQLdb
>
> Everytime I run "python2.4 cleanup.py wrkstnbs" I get the following error:
>
> Traceback (most recent call last):

Have you snipped any traceback entries here? You say you are running
cleanup.py but the first traceback entry is from purge_client.py!!

You should first fix that, so that you've got the full story. My guess
is that something along that trail is invoking another instance of the
Python interpreter and somehow that instance is 2.5, not 2.4. I can't
imagine how those 2.5-related entries would otherwise get into
sys.path

Suggestions: (1) where you are debug-printing sys.path, also print
sys.version and sys.argv[0] ... and do debug-printing at more places
between start and error.
(2) run "python2.4 -vv cleanup.py wrkstnbs" and look for the first
mention of 2.5 (indicating something has manipulated sys.path), or
sudden cessation of -vv output (indicating a new instance of python is
running without -vv), or some other phenomenon ...

>   File "purge_client.py", line 22, in <module>
>     import MySQLdb
>   File
> "/prod/bacula/local/lib64/python2.4/site-packages/MySQLdb/__init__.py", line
> 27, in <module>
>     import _mysql
> ImportError: /prod/bacula/local/lib64/python2.4/site-packages/_mysql.so:
> undefined symbol: Py_InitModule4

What happens when you run python2.4 and at the interactive prompt do
>>> import _mysql
? Is there a possibility that you installed 2.5 MySQLdb into the 2.4
hierarchy? [could be a stupid question from a windows guy; this may be
a non-problem on linux]

Is this the first thing that you've tried after installing 2.5, or the
only problem found in an exhaustive regression test of all your apps
using 2.4, or somewhere in the middle?

[big snip]

HTH,
John