On Wed, 15 Jul 2015 07:19:53 -1000
Eric Firing efir...@hawaii.edu wrote:
John, if you haven't already done so, please escalate this to a github
issue.
Will do...
Cheers,
John
--
Don't Limit Your Business. Reach for
It is not clear to me that 4202 would fix it, and I think 4202 has a
basic problem of its own.
John, if you haven't already done so, please escalate this to a github
issue.
Eric
On 2015/07/15 4:58 AM, Thomas Caswell wrote:
The PR to fix this is still open
Hello all.
I had MatPlotLib 1.3.1 installed, and decided to upgrade to 1.4.3. I compiled
the
.tar.gz package, which went without a hitch (except for a number of warnings
from gcc). Installation also completed without problems.
But, on running the same simple plot I was working on, no plot was
We have been recently fixing a bunch of issues in the macosx backend (which
is default on Macs). Having the circle be dotted sounds exactly like the
sort of problem that would be caused by some of the bugs we are addressing.
I think we have some of the fixes committed to the master branch, so if
Hello again,
I've posted these two issues in separate mails, as I suspect they're
actually different problems.
This error is particular to the default version of MacOSX's matplotlib
version 1.4.3:
When doing a simple plot:
import matplotlib.pyplot as plt
def test_plot():
x = range(11)
If your backend is set to Agg, then no interactive window will appear upon
call to show(). Agg is intended for headless servers. What might be
happening is that somewhere, you have Agg set as the default backend.
Ben Root
On Wed, Jul 15, 2015 at 10:16 AM, John Coppens j...@jcoppens.com wrote:
The Agg backend is a non-gui backend, it just saves to file. The `TkAgg`
and `GtkAgg` are gui backends (which are more of front ends, but I digress)
which show the output of Agg in a gui window (and provide a layer for
handling user interaction).
I suspect that how ever your 1.3.1 was installed
The PR to fix this is still open (
https://github.com/matplotlib/matplotlib/pull/4202).
Tom
On Wed, Jul 15, 2015 at 10:29 AM John Coppens j...@jcoppens.com wrote:
Hello again,
I've posted these two issues in separate mails, as I suspect they're
actually different problems.
This error is
