Red Hat Bugzilla – Bug 842870
python-basemap cannot be imported in epel6
Last modified: 2015-04-22 18:49:09 EDT
On a rhel6.3 box: % python Python 2.6.6 (r266:84292, May 1 2012, 13:52:17) [GCC 4.4.6 20110731 (Red Hat 4.4.6-3)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from mpl_toolkits.basemap import Basemap Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib64/python2.6/site-packages/mpl_toolkits/basemap/__init__.py", line 38, in <module> import pyproj, sys, os, math, dbflib File "/usr/lib64/python2.6/site-packages/mpl_toolkits/basemap/pyproj.py", line 48, in <module> from _proj import Proj as _Proj File "c_numpy.pxd", line 76, in _proj (src/_proj.c:3234) ValueError: numpy.dtype does not appear to be the correct type object
I see the same issue. I think this comes from the recent numpy upgrade. I rebuilt the basemap rpm and it works now.
Devrim kicked off a build. http://koji.fedoraproject.org/koji/taskinfo?taskID=4342411
python-basemap-0.99.4-11.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/python-basemap-0.99.4-11.el6
https://admin.fedoraproject.org/updates/python-basemap-0.99.4-11.el6
Package python-basemap-0.99.4-11.el6: * should fix your issue, * was pushed to the Fedora EPEL 6 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing python-basemap-0.99.4-11.el6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-6551/python-basemap-0.99.4-11.el6 then log in and leave karma (feedback).
This seems to work here. ;) thanks.
python-basemap-0.99.4-11.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
thank you guys for taking care of this. I'm at a remote radar site at the moment and I don't have an EPEL system with me. Which reminds me I need to make a formal announcement about my upcoming one month of completely off the grid status. -jef
I think this bug may have come back. As of today, 9 July 2014, on a redhat 6.5 machine: [gsh@localhost local_place]$ python Python 2.6.6 (r266:84292, Nov 21 2013, 10:50:32) [GCC 4.4.7 20120313 (Red Hat 4.4.7-4)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from mpl_toolkits import basemap Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib64/python2.6/site-packages/mpl_toolkits/basemap/__init__.py", line 38, in <module> import pyproj, sys, os, math, dbflib File "/usr/lib64/python2.6/site-packages/mpl_toolkits/basemap/pyproj.py", line 48, in <module> from _proj import Proj as _Proj File "c_numpy.pxd", line 76, in _proj (src/_proj.c:3234) ValueError: numpy.dtype does not appear to be the correct type object >>> import numpy >>> print numpy.__version__ 1.8.1 >>>
(In reply to Gregory Hennessy from comment #9) > >>> print numpy.__version__ > 1.8.1 Yeah, that's likely not going to work. We're expecting numpy 1.4.1 in EL6: numpy.x86_64 1.4.1-9.el6 @rhel-6-server-rpms See also new bug #1125032