From: John Hunter <jdhunter@ac...> - 2006-03-29 17:36:35
>>>>> "Tom" == Tom Loredo <loredo@...> writes:
Tom> Hi John,
Tom> I hate to nag you about this, but I'm being nagged myself!
Tom> After boasting about Python to my colleagues, I'm glad to
Tom> have them interested in it, but it's proving embarassing that
Tom> it's so troublesome just to install it. I haven't had such
Tom> problems on several other Mac and Linux machines, so there is
Tom> probably something fishy about his OS X install, but I can't
Tom> figure out what it is. Do you have any thoughts on this? Is
Tom> X11 necessary, for example? I'm really at a dead end
Tom> regarding how to pursue this.
I can help you walk through the diagnosis a bit
Fire up a python shell
* does import pylab cause a segfault?
If so, try importing these 1 by 1 and see where the problem is
..maybe others but that is a good start
If not, eg you need to try and make a figure to trigger the import, we
want to enable extra verbose debugging.
Flush your build subdir, and edit setup.py to set VERBOSE = True and
recompile (capture the build to a file and post it). This will cause
the extension code to generate verbose output which may isolate the
problem. Run your test code with --verbose-debug-annoying and be
prepared for a deluge of messages.
You might want to flush ~/.matplotlib occassionaly to make sure there
is not something messing with you in the cache.
One possibility is that you are picking up multiple zlibs or libpngs
or libfreetypes, which can lead to segfaults. Try inspecting your
system to make sure you know which of these libsa are installed, which
versions, and where.
I'm putting this back on list in case your response triggers a
lightbulb in some resident OSX expert's head.
> LocalWords: occassionaly