Bug 929383

Summary: Matplotlib not working with Python 3
Product: [Fedora] Fedora Reporter: Amit Saha <asaha>
Component: python-matplotlibAssignee: Thomas Spura <tomspur>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: amcnabb, amitsaha.in, bkabrda, dmalcolm, ebaak, gwync, jonathan.underwood, jspaleta, paulo.cesar.pereira.de.andrade, thibault.north, tomspur
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-10 13:18:06 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 Amit Saha 2013-03-30 10:05:17 UTC 
Description of problem:

I am not sure if this is an upstream issue, so reporting this here. I have python3-matplotlib-1.2.0-8.fc18.x86_64 installed. 

When I tried to execute the histogram demo [1], I get this traceback [2].


[1] http://matplotlib.org/examples/api/histogram_demo.html
[2] http://pastebin.ca/2345456

Version-Release number of selected component (if applicable):


How reproducible:

Always

Steps to Reproduce:
1. Install python3-matplotlib
2. Download the histogram demo.
3. Run 
  
Actual results:

Traceback.

Expected results:

Plot.

Additional info:
Comment 1 Amit Saha 2013-03-30 10:59:22 UTC 
So, it turned out after I asked the question on SO [1] that it is an issue with font_manager.py (/usr/lib64/python3.3/site-packages/matplotlib/font_manager.py). I had to set USE_FONTCONFIG = False in this module and it worked.


[1] http://stackoverflow.com/questions/15717119/python-3-and-matplotlib-lissue-on-linux
Comment 2 Amit Saha 2013-03-30 14:32:33 UTC 
Upstream bug filed: https://github.com/matplotlib/matplotlib/issues/1873
Comment 3 Thomas Spura 2013-04-10 13:18:06 UTC 

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