Strange Build problem....

[Steve Dickson]

On 15/01/13 15:43, Toshio Kuratomi wrote:
> The try: except: is swallowing all errors here.  Getting a more verbose
> traceback may help diagnose.  You can remove the try: except: and dedent the
> remaining code one level to get the actual traceback in the build.log.
This is exactly what I did:

# cat /tmp/test.py
import os, posix, stat, sys

import matplotlib
matplotlib.use('Agg')
import matplotlib.pyplot as plt
import matplotlib.font_manager as fm

and here is the traceback

raceback (most recent call last):
  File "/tmp/test.py", line 5, in <module>
    import matplotlib.pyplot as plt
  File "/usr/lib64/python2.7/site-packages/matplotlib/pyplot.py", line 26, in <module>
    from matplotlib.figure import Figure, figaspect
  File "/usr/lib64/python2.7/site-packages/matplotlib/figure.py", line 34, in <module>
    import matplotlib.colorbar as cbar
  File "/usr/lib64/python2.7/site-packages/matplotlib/colorbar.py", line 29, in <module>
    import matplotlib.collections as collections
  File "/usr/lib64/python2.7/site-packages/matplotlib/collections.py", line 23, in <module>
    import matplotlib.backend_bases as backend_bases
  File "/usr/lib64/python2.7/site-packages/matplotlib/backend_bases.py", line 37, in <module>
    import matplotlib.widgets as widgets
  File "/usr/lib64/python2.7/site-packages/matplotlib/widgets.py", line 17, in <module>
    from lines import Line2D
  File "/usr/lib64/python2.7/site-packages/matplotlib/lines.py", line 25, in <module>
    from matplotlib.font_manager import FontProperties
  File "/usr/lib64/python2.7/site-packages/matplotlib/font_manager.py", line 1325, in <module>
    _rebuild()
  File "/usr/lib64/python2.7/site-packages/matplotlib/font_manager.py", line 1312, in _rebuild
    fontManager = FontManager()
  File "/usr/lib64/python2.7/site-packages/matplotlib/font_manager.py", line 994, in __init__
    self.defaultFont['afm'] = self.afmfiles[0]
IndexError: list index out of range

So it appears to be a problem with matplotlib.... 

My question is why is this happen *only* in a mock environment??? 
Is it  because that environment does not have a needed package??? 

thanks for the time... 

steved.