Bug 1177319

Summary: Import of Matplotlib Basemap fails
Product: [Fedora] Fedora Reporter: Jay <jan.zoerner>
Component: python-basemap-dataAssignee: Jef Spaleta <jspaleta>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 21CC: adrian, gwync, josdekloe, jspaleta, kjh
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-20 10:45:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jay 2014-12-26 05:53:52 UTC 
Description of problem:
Import of matplotlib basemap fails under Fedora 21, because the matplotlib-basemap data cannot be found (python-basemap-data).

Version-Release number of selected component (if applicable):
python-basemap-data 1.0.7 2.fc21
python-basemap 1.0.7 4.fc21

How reproducible:
Since the data directory does not exist the import will always fail.

Steps to Reproduce:
1. install python-basemap, python-basemap-data and all its dependencies
2. import basemap in a python shell: from mpl_toolkits.basemap import Basemap

Actual results:
IOError: proj data directory not found. Expecting it at: /usr/lib64/python2.7/site-packages/mpl_toolkits/basemap/data
This path does not exist.

Expected results:
succesfull import of matplotlib-basemap
Comment 1 Adrian Reber 2015-01-12 12:41:03 UTC 
This is also discussed here: http://stackoverflow.com/questions/27505708/import-basemap-fails-under-fedora-21
Comment 2 Jos de Kloe 2015-03-20 10:03:25 UTC 
*** Bug 1177903 has been marked as a duplicate of this bug. ***
Comment 3 Jos de Kloe 2015-03-20 10:45:47 UTC 
issue has been fixed with update python-basemap-1.0.7-6.fc21, see:
https://bugzilla.redhat.com/show_bug.cgi?id=1177052

*** This bug has been marked as a duplicate of bug 1177052 ***