2010/4/14 Jon Moore <jonr_mo...@yahoo.co.uk>: > Hi, > > Find attched log.txt generated when trying to run your script. Any > thoughts?
Sounds like a typo to me. Please give the new version of crashtest.py
a try, it prints stack tracebacks for each import statement into the
file, so we *should* be able to track it down with this.
The log file created with "#import calendar" commented out is already
20kB large, so maybe too large for the list. Your will be expected to
be some megabytes I guess :-( but only the last traceback should
matter.
Also I noticed that our import history is *quite* different. Make a
vimdiff or similar of my old log.txt and the log.txt you provided.
Note that I cannot make a working import because I have no mpl
currently on this MacBook.
Here comes an example output:
import operator, traceback follows:
File "crashtest.py", line 24, in <module>
import calendar
File "crashtest.py", line 18, in new_import
return old_import(name, *args, **kwargs)
File
"/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/calendar.py",
line 10, in <module>
import locale as _locale
File "crashtest.py", line 18, in new_import
return old_import(name, *args, **kwargs)
File
"/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/locale.py",
line 202, in <module>
import re, operator
File "crashtest.py", line 17, in new_import
traceback.print_stack()
so far,
hth,
Friedrich
crashtest.py
Description: Binary data
------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev
_______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
