My guess is that Winston is not the problem, but rather Gtk or Tk (whatever is being loaded by Winston and PyPlot). They are incredibly unstable, and it's way too easy to load incompatible libraries into your process at the same time.
Do you know which package(s) are forcing Winston on you? Also could you post the GUI backends that both Winston and PyPlot are currently using? On Fri, Nov 20, 2015 at 8:53 AM, Peter Kovesi <[email protected]> wrote: > I am encountering a problem whereby it seems that if Winston is imported > any subsequent calls to PyPlot produce a fatal Python error and the REPL > crashes > > > using PyPlot > > plot(rand(20)) # All is OK > > import Winston # lots of deprecation messages > > plot(rand(20)) # crash > > Fatal Python error: PyEval_RestoreThread: NULL tstate > > Current thread 0x00007fff788b9300 (most recent call first): > > signal (6): Abort trap: 6 > > __pthread_kill at /usr/lib/system/libsystem_kernel.dylib (unknown line) > > > I do not want to use both Winston and PyPlot but if I load a package that > happens to import Winston then any use of PyPlot is impossible > > Do others encounter this problem, or is this the result of some quirk in > my installation? > > > OSX 10.10.5 > > Julia 0.4.1 > > PyCall 1.2.0+ > > PyPlot 2.1.1 > > Winston 0.11.13 > > Anaconda Python 3.5.0-1 >
