On 14 Aug 2014, at 11:40 pm, Chris Barker <chris.bar...@noaa.gov> wrote:
> On Thu, Aug 14, 2014 at 12:07 PM, Eric Firing <efiring.oc...@gmail.com> wrote:
> but as far as I can see, on OSX, there is no *advantage* to non-framework
> python. Is this correct?
>
> Suggestion for anaconda:
> make bin/python a link to ../python.app/Contents/MacOS/python
>
> NOTE: the python.org python build has been doing this (or something like it)
> for years and many versions -- I had gotten pretty used to it and was pretty
> annoyed when I discovered Anaconda keeps anon-framework binary as the default.
>
> It was annoying enough that I had to explicitly call pythonw (or alter the #!
> line) for my wxPython scripts, but with ipython it's even worse -- how would
> I start up ipython with a framework build?
>
> NOTE: if the Anaconda folks really think there is a real downside to using
> the framework executable for the default python, maybe the ipython start up
> script could use pythonw ?
>
> Eric - have you tried recent MPL with the python.org builds to confirm the
> issue? I'm a bit surprised that it would even semi-work -- when I try
> wxPython with the regular executable, I get an error message and it wont run
> at all.
>
Just to make sure I understand - this is about whether the MPL macosx backend
would run with non-framework
Python at all? It certainly should not, as _macosx.m has been enforcing an
error in this case for some versions.
That put aside, when I disable the error at the end of _macosx.m I found the
OSX backend to still work as it used
to under OS X 10.9 with the Fink Python installation (which is not built as a
framework, and unfortunately unlikely
to change in foreseeable time). I.e. the only obvious problem is the lack of
control by the window manager.
Overall I still find it to perform better than any of the alternative backends.
But having switched to PyQT4 as the
default backend due to the above Fink troubles, I did notice some oddities
under Mavericks. I have no idea if they
are related to the problems Eric had originally reported, but they are clearly
Mavericks-specific:
When using MPL with ipython —pylab and the Quartz version of PyQT4, the
interpreter seems to be slow down
extremely after running for a little while. Weirdly this is not connected to
any graphics display and in fact happens
even without any plotting window opened, i.e. the ipython shell just randomly
becomes completely unresponsive
and hangs for several seconds on simple tasks like typing or navigating through
history. The plotting itself actually
does not appear to perform any worse than it used to under Mountain Lion.
None of this seems to occur with the X11 variant of PyQT4.
When launching ipython without the —pylab flag and loading MPL later (e.g. with
‘import matplotlib’ in the ipython
profile), none of these stalls or hangups occur, but plots sometimes seem not
to refresh properly even with a
plt.draw() and one has to manually resize the plot window to force redrawing of
the figure.
This might be primarily a PyQT4 or Ipython issue, but obviously it is somehow
connected to the pylab mode of Ipython.
Cheers,
Derek
------------------------------------------------------------------------------
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
