I am still getting this error, this time with matplotlib.pyplot.matshow, and
I do not get any plot. This bug really needs to be fixed!
--
View this message in context:
http://matplotlib.1069221.n5.nabble.com/Error-in-atexit-run-exitfuncs-tp43566p43947.html
Sent from the matplotlib - users
Can you provide a minimal example that will trigger the bug?
From the description you have given we don't have enough information
to diagnose the problem.
Ben thinks this is related to some long-standing issues, if you could
help us track them down it would be greatly appreciated.
Tom
On Mon,
plt.matshow([[0.0]])
It crashes with the FigureManagerGTK3Cairo error.
Keith
-Original Message-
From: Thomas Caswell [mailto:tcasw...@gmail.com]
Sent: 15 September 2014 13:23
To: Briggs,KM,Keith,TUB2 R
Cc: matplotlib-users@lists.sourceforge.net
Subject: Re: [Matplotlib-users] Error
@lists.sourceforge.net
Subject: Re: [Matplotlib-users] Error in atexit._run_exitfuncs
Can you provide a minimal example that will trigger the bug?
From the description you have given we don't have enough information to
diagnose the problem.
Ben thinks this is related to some long-standing issues
no attribute 'canvas'
From: Thomas Caswell [tcasw...@gmail.com]
Sent: 15 September 2014 13:38
To: Briggs,KM,Keith,TUB2 R
Cc: matplotlib-users@lists.sourceforge.net
Subject: Re: [Matplotlib-users] Error in atexit._run_exitfuncs
What versions of things
I am running matplotlib 1.3.1 under Ubuntu 13 and python3.
Everything works fine, but I get this message every time:
Error in atexit._run_exitfuncs:
AttributeError: 'FigureManagerGTK3Cairo' object has no attribute 'canvas'
What does it mean, and how do I stop it?
Keith
What it means, specifically, is that one (or more) figure objects still in
memory at the time of exiting the python interpretor are missing the
expected canvas attribute. I see this happen in various backends from time
to time. The best I can figure is that somehow, the destructor for the
figure