[Python-modules-team] Bug#535855: matplotlib._path

Fabrice Silva silva at crans.org
Tue Jul 7 22:48:15 UTC 2009

Le mardi 07 juillet 2009 à 09:18 +0200, Thomas Viehmann a écrit :
> Hi Fabrice, Sandro,
> Sandro asked for debugging ideas, so here is mine:
> Fabrice, could you please see what sys.path is when the loading fails 
> and also try to load the module with
>    python -v -v -c 'import matplotlib.transform' 2> /tmp/import_log.txt
> ?
        >>> for tmp in sys.path:
        ...     print tmp

Then see http://fsilva.perso.ec-marseille.fr/visible/import_log.txt

In particular, near line 1840
$grep -A5 -B3 -n -m1 Traceback /tmp/import_log.txt
        1835-import datetime # dynamically loaded from /usr/lib/python2.5/lib-dynload/datetime.so
        1836-# trying /usr/share/pyshared/matplotlib/_path.so
        1837-# trying /usr/share/pyshared/matplotlib/_pathmodule.so
        1838-# trying /usr/share/pyshared/matplotlib/_path.py
        1839-# trying /usr/share/pyshared/matplotlib/_path.pyc
        1840:Traceback (most recent call last):
        1841-  File "<string>", line 1, in <module>
        1842-ImportError: No module named _path
        1843-# clear __builtin__._

> P.S.: I think that technically 'grave' implicitly includes 'useless for 
> everyone', so this should be 'important', but seeing this resolved is 
> more interesting than setting the severity.
I agree.

Fabrice Silva
Laboratory of Mechanics and Acoustics - CNRS
31 chemin Joseph Aiguier, 13402 Marseille, France.

More information about the Python-modules-team mailing list