On Jan 9, 10:58 pm, "David Grant" <[EMAIL PROTECTED]> wrote: > Well it is still trying to import from /root/.python-eggs/... I would also > be interested in knowing why you are doing things as root, but I guess > that's not important... > > It's still trying to import from /root/.python-eggs so get that out of your > python path. Run python and then > > import sys > print sys.path > > Remove /root/.python-eggs or any other paths. > > Since it is happening on all three SUSE installs, well I don't know what to > think. I've never used eggs before and I never compile anyting from scratch > unless I really have to (except using Gentoo's package manger). Any > python/mysql/mysqldb are things you should never need to compile from > scratch (unless you really need to). And no offense but if you were someone > who really needed to compile them from scratch....I would have thought you > would be able to solve this problem yourself. I don't even use Gentoo > anymore, too much work. > > --
Hi David. Thanks for the responses. Believe me, I too wondered why I needed to build things from scratch to get them to work. I couldn't imagine every newbie would be forced to compile all related software. But as mentioned previously in this thread, when I searched for solutions this error: ImportError: /home/rmazur/.python-eggs/MySQL_python-1.2.2-py2.5-linux- i686.egg-tmp/_mysql.so: undefined symbol: __pure_virtual ...nearly every one of them (that I looked at) cited the likely cause to be MySQL and Python being compiled by different compilers. This was the sole reason I chose to compile myself, and did so as a process of elimination. That being said, I am weary of using the package managers of Linux distributons because when things go sideways, it is sometimes hard to tell how things are tied together and what dependencies might be causing conflict. Thus my preference is to download binaries if possible. Regarding running as root...I was doing so to initially to remove the possibility of permission issues causing my problems. This is mostly due to me being completely new to Python. As you likely know from other langauges, you can ocassionally hit error text from compilers or run-time errors that cite a, b or c being an error when in reality all it is is a permission problem. Once I have a handle of how to solve my current problem, what caused it, etc, then I will wipe the slate clean and set things up properly for long-term usage. I will try your other suggestion, and thank you again for your patience as I dip my toe into the Python world...I am just at the beginning of learning what the errors mean, the appropriate config, what an egg even is....etc. Thanks for your help. Rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
