I posted as an issue over on PyPlot. I got a reply about Python but not about the problem.
Please point out how I have been negative. I've tried to provide information and one other user confirms that he has also seen the problem. I thought I was being pretty clear to just ask for clues or pointers to other things I can try or look at it. On Tuesday, November 10, 2015 at 10:50:04 AM UTC-8, Tom Breloff wrote: > > Lewis: There are a couple things to note: > > - This belongs as a PyPlot issue... it's not really appropriate for > julia-users > - I think people have been slow to help you, not because you're a > "noob", but because of your extreme negativity so far. > > You've spent enough time on this that you're probably also the most > qualified to solve it. > > On Tue, Nov 10, 2015 at 1:34 PM, <le...@neilson-levin.org <javascript:>> > wrote: > >> I'd still really like help with this. >> >> Here are some possible problems with the way just the first figure is >> being handled within PyPlot: >> 1. being put in the figure_queue, which holds figures for >> IJulia--this shouldn't be happening as I am not using IJulia in this case; >> 2. somehow matplotlib is losing it: the close() function in PyPlot is >> a straightforward pycall to put[:close]--with a figure argument f. But, >> when you plot without defining a figure first there is no figure to >> reference. Calls to close don't pass any argument. It's not clear why >> this would be a problem because everything works for the 2nd and all >> subsequent plots created WITHOUT first starting an identified figure. >> 3. gcf() can't find the figure. When I run gcf after the first plot, it >> actually creates a NEW figure because it doesn't see that any figure exists >> (even though it is there because matplotlib created it and it's on the >> screen in a tk window). >> >> So, number 3 seems to point to the symptom that in the handoff between >> matplotlib and pyplot, the first figure created is getting lost. Perhaps >> someone can point me to the next level so I can keep trying to diagnose >> this. >> >> It seems folks aren't so interested in problems that are rarely seen and >> are reported by Noobs. We were all once noobs. I may be a permanent noob. >> I realize there are cooler things to focus on in the future trajectory of >> Julia, but this is an actual problem. >> >> >> On Monday, November 9, 2015 at 11:07:50 AM UTC-8, Ethan Anderes wrote: >>> >>> I have noticed something similar. >>> >>> For example, if I do: >>> >>> julia> using PyPlot >>> >>> julia> figure(1) >>> >>> julia> plot(sin(1:10)) >>> >>> julia> figure(2) >>> >>> julia> plot(cos(1:10)) >>> >>> then close the first figure (by clicking the red button with my mouse) I >>> get a spinning beach ball. I’m on OSX 10.11.1 using Anaconda python. PyPlot >>> is at version "PyPlot"=>v"2.1.1+" and my system info is >>> >>> julia> versioninfo() >>> Julia Version 0.4.1-pre+16 >>> Commit 2cdef5d (2015-10-24 06:33 UTC) >>> Platform Info: >>> System: Darwin (x86_64-apple-darwin15.0.0) >>> CPU: Intel(R) Core(TM) i7-4850HQ CPU @ 2.30GHz >>> WORD_SIZE: 64 >>> BLAS: libopenblas (USE64BITINT DYNAMIC_ARCH NO_AFFINITY Haswell) >>> LAPACK: libopenblas64_ >>> LIBM: libopenlibm >>> LLVM: libLLVM-3.3 >>> >>> >>> >>> >> >
