Re: [matplotlib-devel] macosx broken on py3.4 (homebrew, anaconda)

2014-08-14 Thread Thomas Caswell 
Can you make a blocker issue for this?

Is it worth looping the ipython devs in on this email/issue as well?



On Wed, Aug 13, 2014 at 8:13 PM, Eric Firing  wrote:
> On 2014/08/13, 1:19 PM, Eric Firing wrote:
>> Unless there is something odd about my machine and attempted setups, we
>> have a very bad situation.  I have OS X 10.9 (Mavericks).  I am seeing
>> the same problem with homebrew python and pip-installed numpy,
>> pip-installed mpl from git 1.4rc3, and from Anaconda 2.0.1, all with
>> python 3.4.
>>
>> Do the normal thing: fire up ipython, use %matplotlib magic, import
>> numpy and pyplot, make a plot.  The macosx backend comes up as the
>> default.  A plot appears, but it is not interactive.
>>
>> Maybe this is related to the framework vs non-framework build question.
>>   In a way, I don't care--the important point is that using *common*
>> methods of trying to get started with ipython and mpl on up-to-date
>> python, one immediately runs into a basic failure.
>>
>> If this can't be fixed *fast*, I suggest we make the macosx backend
>> available only by special request, not by default, as of a 1.4 release.
>>
>> Yes, this can go to a github issue if appropriate, but first I want to
>> get thoughts from a wider audience.
>>
>> Comments?
>>
>> (I'm wondering why this hasn't driven someone else nuts some time
>> ago--hasn't anyone else run into this?)
>>
>> Eric
>
> Clue: my first try with homebrew was in a virtualenv.  Now I installed
> everything directly, without the virtualenv, and the first plot trial
> worked.  Then I tried restarting ipthon and using "%matplotlib qt".
> Plotting was OK, but after closing the plot window and going away for a
> bit, upon coming back, the ipython terminal was extremely sluggish.
> App-nap problems?  I was having similar response problems in some
> earlier trials as well, with ipython in anaconda.  I thought all this
> was supposed to have been cleared up by now...
>
> I went back to anaconda, and verified I am still getting the
> unresponsive window--it can't even be resized.
>
> Eric
>
> --
> ___
> Matplotlib-devel mailing list
> Matplotlib-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel



-- 
Thomas Caswell
tcasw...@gmail.com

--
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] [Anaconda Support] OSX: why not make "python" invoke the framework?

2014-08-14 Thread Chris Barker 
On Thu, Aug 14, 2014 at 12:07 PM, Eric Firing 
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.



>  (On 2.7, I think this would also make wxpython applications work, but I
> haven't checked recently.)
>

yup -- it should -- does for me anyway.

If there is some reason why this default to a framework is not a good idea,
> and/or cannot be implemented very soon in Anaconda, then I think we need to
> immediately remove macosx as a default in matplotlib.  A situation where a
> new Anaconda user fires up ipython and tries to plot, and it fails, is
> intolerable.


for what it's worth, I get odd os-x errors trying to se default MPL with
Anaconda as well -- haven't tried pythonw for that yet. (kludged it by
using the Agg back end only)


-- 

Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R(206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115   (206) 526-6317   main reception

chris.bar...@noaa.gov
--
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel