py34-matplotlib: 'Py::Exception' after invoking 'from pylab import *'

[RivetBenoit (Benoit Rivet)]

Launching the python shell and invoking

from pylab import *

gives the following result :

terminate called after throwing an instance of 'Py::Exception'
Abort trap

I am using an up to date MacPort on Mac OS X.5 PPC (G4 iMac), with Python 3.4.

[ryandesign (Ryan Carsten Schmidt)]

I assume py34-matplotlib is the port that installed this.

Could you attach the crash log file, please? It should be in ~/Library/Logs/DiagnosticReports

[RivetBenoit (Benoit Rivet)]

I added the crash report found in ~/Library/Logs/CrashReporter (this is MacOS X.5...) as requested and I noticed since then that my config is not quite up to date. The command

port outdated

returns quite a lot of ports, including :

py34-matplotlib                1.4.2_0 < 1.4.3_0
py34-numpy                     1.9.1_0 < 1.9.2_2         
py34-scipy                     0.14.0_0 < 0.16.0_1

I shall upgrade and tell you if the bug is still there after upgrading. This is however a tedious process : I was installing py34-pyside this morning when I reported this pylab bug; and MacPorts has been building qt4-mac since.

So don't expect any news on this bug before a day or two or more :-)

[petrrr]

Cc Me!

[RivetBenoit (Benoit Rivet)]

Replying to petr@…:

I reinstalled MacPorts from scratch, then python34 and py34-matplotlib, found out that the bug still exists (on Mac OS X.5 PPC) and narrowed down the bug to a couple of imports in pylab.py.

In the python3 console

import matplotlib.finance

or

import matplotlib.pyplot

raises the error

terminate called after throwing an instance of 'Py::Exception'
Abort trap

Commenting the lines corresponding to these imports helps import pylab without error... But what's the point of using matplotlib if pyplot is not available ?

[RivetBenoit (Benoit Rivet)]

Cc Me!

[RivetBenoit (Benoit Rivet)]

Crash after importing matplotlib.pyplot in the python3 console

[RivetBenoit (Benoit Rivet)]

After tracking down the bug down, I found out that the following import in the python3 console :

import matplotlib.font_manager

raises the fatal error

terminate called after throwing an instance of 'Py::Exception'
Abort trap

Delving into font_manager.py, I tried and change line 66 from font_manager.py :

USE_FONTCONFIG = False

to

USE_FONTCONFIG = True

and everything seems to work fine, until I try to save a simple figure and the fatal 'Py:Exception' error shows up...

[seanfarley (Sean Farley)]

I am using an up to date MacPort on Mac OS X.5 PPC (G4 iMac)

If someone else wants to help out, then by all means, please do. I don't really have the time nor the resources to debug bugs on a PPC machine. I'm going to mark this as 'wontfix' for now but we can reopen if need be.

[RivetBenoit (Benoit Rivet)]

I should add that everything works fine with python33; which means that something broke between Python33 and Python34...

[RivetBenoit (Benoit Rivet)]

Another update on the bug : everything was fine with matplotlib 1.3.1_4 and python33; however, upgrading py33matplotlib to version 1.4.3_0 causes the same problem with python33 and python34. So something broke between matplotlib 1.3 and 1.4.

I am now able to use matplotlib with Python34 after downgrading to the last version 1.3 provided by macports. Specifically :

cd ~/macports
svn checkout -r 121194 https://svn.macports.org/repository/macports/trunk/dports/python/py34-matplotlib
cd py34-matplotlib
sudo port install

enabled me to install the last revision before upgrading matplotlib to version 1.4.x

After upgrading to a new version of matplotlib, if the bug has not disappeared :

sudo port activate py34-matplotlib @1.3.1_4+cairo+tkinter

enables me to downgrade again.