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
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
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)
On Thu, Aug 14, 2014 at 12:07 PM, Eric Firing <efiring.ocean@...149...> wrote:
Christopher Barker, Ph.D.
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