matplotlib-devel Mailing List for matplotlib

Pandas has some nice tools to make faceted plots -- small multiples of
plots where data is grouped by category (
http://pandas.pydata.org/pandas-docs/stable/rplot.html). However, I think
there would be value in having this functionality built into matplotlib.
Mainly:

1. Not every dataset lives in a dataframe
2. The pandas library mimics the ggplot interface, and some people would
prefer an interface closer to matplotlib
3. Properly implemented, I think a matplotlib facet system would enable a
wider variety of faceted plots than the pandas tools.

I've taken a stab at this, and came up with an interface that I think has
potential. This currently exists as a separate repository at
https://github.com/ChrisBeaumont/mplfacet, and an example notebook at
http://bit.ly/17u1JzP

There two basic ways to use a facet object:

Facet(key, data).method()

will group one or more data arrays by key, and build a subplot for each
group by calling method (which is any axes plot method). Alternatively,

for item in Facet(key, data):
    x, y = item.data
    item.axes.scatter(x, y)

sets up the subplots and groups the data for you, but gives you more
freedom to populate each subplot however you like.

Is there interest in building this into matplotlib? If so, I would like to
polish it up and submit a PR.

Cheers,
Chris

When a test fails on Travis, it will now upload the failed result images 
to Amazon S3.  Just scroll down to the bottom on the Travis console 
output, and there will be a URL there to a .tar.bz2 data containing the 
test results.  Handy.

Details:

Note, that we don't pay anything to upload to S3, only to download. And 
if it's only us developers really using these files, our download fees 
should be quite low.  In order to save storage costs, these result files 
are automatically deleted after 30 days.

Cheers,
Mike

You provide a single standalone example to reproduce this. Most of our 
files have |from __future__ import division|, so I'm not entirely sure 
what could be going on...

Mike

On 08/28/2013 11:56 AM, Benjamin Root wrote:

>
>
> On Wed, Aug 28, 2013 at 10:45 AM, Neal Becker <ndb...@gm... 
> <mailto:ndb...@gm...>> wrote:
>
>     Autoscaling is producing a different result on p2 vs p3.  Maybe a
>     missed
>     N/M -> N//M ??
>
>     [nbecker@nbecker7 dvbs2x_iter]$ rpm -q python-matplotlib
>     python-matplotlib-1.2.0-14.fc19.x86_64
>     [nbecker@nbecker7 dvbs2x_iter]$ rpm -q python3-matplotlib
>     python3-matplotlib-1.2.0-14.fc19.x86_64
>
>
> Cheers!
> Ben Root
>
>
> ------------------------------------------------------------------------------
> Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
> Discover the easy way to master current and previous Microsoft technologies
> and advance your career. Get an incredible 1,500+ hours of step-by-step
> tutorial videos with LearnDevNow. Subscribe today and save!
> http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

On Wed, Aug 28, 2013 at 10:45 AM, Neal Becker <ndb...@gm...> wrote:

> Autoscaling is producing a different result on p2 vs p3.  Maybe a missed
> N/M -> N//M ??
>
> [nbecker@nbecker7 dvbs2x_iter]$ rpm -q python-matplotlib
> python-matplotlib-1.2.0-14.fc19.x86_64
> [nbecker@nbecker7 dvbs2x_iter]$ rpm -q python3-matplotlib
> python3-matplotlib-1.2.0-14.fc19.x86_64
>
>
Cheers!
Ben Root

Thanks Andreas,

> I couldn't find any test runner script / method.

There is currently no "python setup.py tests" type runner (which would be
welcomed), but the obvious test runner is to use "nose" - something like
"nosetests cartopy" should do the trick. It'd also be very easy to put a
function in the cartopy.tests module so that one may run the tests with
"import cartopy.tests; cartopy.tests.run_all()" - if that'd encourage you
to run the tests, I'd be supportive of adding it :-)

> the test_img_nest.py script fails on my machine

Hmmm, yes, it makes use of the hardcoded path based on __file__ of cartopy.
It'd be pretty quick to change this to use the cartopy.config['data_dir']
location, which should be writeable. Would you mind opening an issue or if
you're keen a PR?

> Thanks for making cartopy, this is awesome :)

Cool. Glad you like it - there are still some issues to address, but in
principle it is looking very promising IMHO.

Cheers,

Phil



On 27 August 2013 17:22, andreas-h <li...@hi...> wrote:

> Hi,
>
> I'm in the progress of packaging cartopy for Ubuntu. Some questions about
> the test suite:
>
> - I couldn't find any test runner script / method. It would be handy to
> have
> a script "run_tests.py" which performs all unit tests, or a method
> cartopy.run_tests(), or both. Otherwise, running the tests is a lot of
> manual work (which means it's less likely to happen).
>
> - the test_img_nest.py script fails on my machine (after installing the
> package), because it tries to write to the directory in which cartopy is
> installed. It would be better if filesystem write access would happen in
> some tempdir (which could be automatically cleaned up after the test).
>
> Thanks for making cartopy, this is awesome :)
>
> Cheers, Andreas.
>
>
>
> --
> View this message in context:
> http://matplotlib.1069221.n5.nabble.com/cartopy-test-suite-questions-tp41914.html
> Sent from the matplotlib - devel mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
> Discover the easy way to master current and previous Microsoft technologies
> and advance your career. Get an incredible 1,500+ hours of step-by-step
> tutorial videos with LearnDevNow. Subscribe today and save!
> http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Autoscaling is producing a different result on p2 vs p3.  Maybe a missed
N/M -> N//M ??

[nbecker@nbecker7 dvbs2x_iter]$ rpm -q python-matplotlib
python-matplotlib-1.2.0-14.fc19.x86_64
[nbecker@nbecker7 dvbs2x_iter]$ rpm -q python3-matplotlib
python3-matplotlib-1.2.0-14.fc19.x86_64

Hi,

I'm in the progress of packaging cartopy for Ubuntu. Some questions about
the test suite:

- I couldn't find any test runner script / method. It would be handy to have
a script "run_tests.py" which performs all unit tests, or a method
cartopy.run_tests(), or both. Otherwise, running the tests is a lot of
manual work (which means it's less likely to happen).

- the test_img_nest.py script fails on my machine (after installing the
package), because it tries to write to the directory in which cartopy is
installed. It would be better if filesystem write access would happen in
some tempdir (which could be automatically cleaned up after the test).

Thanks for making cartopy, this is awesome :)

Cheers, Andreas.



--
View this message in context: http://matplotlib.1069221.n5.nabble.com/cartopy-test-suite-questions-tp41914.html
Sent from the matplotlib - devel mailing list archive at Nabble.com.

On 08/20/2013 08:33 PM, Matt Terry wrote:
> That is handy information.  I'll start adding a python.org 
> <http://python.org> target.
>
> How broad coverage do we want?
> 10.6, 10.7, 10.8
> system, python.org <http://python.org> (2.7, 3.3), brew, macports
> virtualenv, no virtualenv
> with/without third party X

Yes, it's a big testing matrix, but I think we can treat it as sparser 
than it really is.

For example, I don't think it matters too much if we test with/without 
third party X with every version number of Python... Time will tell 
exactly what needs to be tested based on bug reports of side cases we 
*didn't* catch.

Also, would it make sense to move your mpl_on_travis_mac project to the 
matplotlib organization (and then add you as a developer over there?)

Mike

>
> The testing matrix blows up pretty quickly.  For those of you with 
> longer memories, where are the corners where things tend to break?
>
> -matt
>
>
>
> On Tue, Aug 20, 2013 at 12:09 PM, Russell E. Owen <ro...@uw... 
> <mailto:ro...@uw...>> wrote:
>
>     A few hints:
>
>     If you just want to build matplotlib for your own computer (and don't
>     care about making an installer that will work on anybody else's) then
>     you can install from source with very little trouble:
>     - You may want to edit setupext.py to limit searching to those
>     dirs that
>     really matter, but this is only needed if you have installed
>     extras that
>     might conflict.
>     - You may want to edit setup.cfg to select a better default back end.
>
>     You have to be much more careful if you want to build a binary
>     installer
>     that can be used by others. I've found that bdist_mpkg works, and I've
>     found it is safest to build on the oldest platform I want the
>     installer
>     to support (for example /usr/X11/lib moved in 10.8 or 10.7 in a
>     way that
>     is forward but not backwards compatible).
>
>     For Apple's python you need install anything; all you need is in
>     /usr/lib and /usr/X11/lib. I have no idea if TkAgg works well.
>
>     For python.org <http://python.org> python you should install a
>     version of Tcl/Tk. I suggest
>     ActiveState Tcl/Tk 8.5.11. Be warned that versions 8.5.12, 8.5.12.1,
>     8.5.13 all have known crashing problems; I have not tried 8.5.14
>     (which
>     came out fairly recently) as 8.5.11 seems to do well enough.
>
>     I've cannot comment on building matplotlib for macports, fink or
>     homebrew.
>
>     -- Russell
>
>     In article <520...@st...
>     <mailto:520...@st...>>,
>      Michael Droettboom <md...@st... <mailto:md...@st...>>
>      wrote:
>
>     > We actually discussed this very issue yesterday in our Google
>     hangout
>     > about continuous integration. We're probably going to need to
>     script a
>     > full setup from a clean Mac + XCode to a working matplotlib
>     development
>     > environment in order to make that happen, and obviously that will be
>     > shared with the world.  Things are even more complex on Windows,
>     and I'd
>     > like to do that there, too.  So stay tuned.
>     >
>     > Mike
>     >
>     > On 08/16/2013 10:02 AM, Paul Hobson wrote:
>     > > Mike,
>     > >
>     > > That's great news. Is there any chance we can look forward to
>     > > "official" instructions for setting up a Mac to develop
>     matplotlib?
>     > >
>     > > I gave up a long time ago and started piecing to together my
>     meager
>     > > PRs in a linux VM.
>     > > -paul
>     > >
>     > >
>     > > On Fri, Aug 16, 2013 at 6:52 AM, Michael Droettboom
>     > > <md...@st... <mailto:md...@st...>
>     > > <mailto:md...@st... <mailto:md...@st...>>> wrote:
>     > >
>     > >     Thanks to the gracious donation from Hans Petter
>     Langtangen and the
>     > >     Center for Biomedical Computing at Simula
>     > >     (http://home.simula.no/~hpl <http://home.simula.no/%7Ehpl>
>     <http://home.simula.no/%7Ehpl>),
>     > >     I now have a new Mac Mini sitting at my desk.  This should
>     allow me to
>     > >     keep on top of changes that affect the Mac builds and to
>     better track
>     > >     down Mac-only issues.
>     > >
>     > >     Stay tuned over the next few weeks and months as we will most
>     > >     likely be
>     > >     using some more of these funds to pay for hosted continuous
>     > >     integration
>     > >     services (as discussed yesterday in our MEP19 Google Hangout).
>     > >
>     > >     Cheers,
>     > >     Mike
>
>
>     ------------------------------------------------------------------------------
>     Introducing Performance Central, a new site from SourceForge and
>     AppDynamics. Performance Central is your source for news, insights,
>     analysis and resources for efficient Application Performance
>     Management.
>     Visit us today!
>     http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
>     _______________________________________________
>     Matplotlib-devel mailing list
>     Mat...@li...
>     <mailto:Mat...@li...>
>     https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
>
>
> ------------------------------------------------------------------------------
> Introducing Performance Central, a new site from SourceForge and
> AppDynamics. Performance Central is your source for news, insights,
> analysis and resources for efficient Application Performance Management.
> Visit us today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Matt,

Thanks for looking into this!  I had already planned to look into 
building on Travis' Mac facilities, so this is a huge timesaver.

Don't forget we also have Option 5 which is to do whatever it takes to 
automate some of these things within matplotlib's setup.py script 
itself.  For example, I'm not opposed to detecting which Python we're 
running (which should be possible from various info available in sys) 
and then setting search paths accordingly. The pkg-config stuff is 
really handy on Linux and MacPorts where it's reliably there, but for 
other Mac environments, we probably should be less reliant on it.

Mike

On 08/23/2013 11:14 AM, Matt Terry wrote:
> I'm banging away at installing MPL on top of python.org 
> <http://python.org>'s python.  I'm at the libfreetype/freetype issue.  
> There seems to be three approaches to getting MPL's dependencies.
>
> 1) install libpng[1] and freetype[2] from source
> 2) install XQuartz[3] and twiddle /opt/X11, /usr/X11 (per Russell's 
> directions[4]) so MPL finds XQuartz's libpng/freetype
> 3) install XQuartz[3] and install pkg-config[5] so MPL can find the 
> cleverly installed libraries
> 4) create the MPL binary installer and use that
>
> Option 1 seems simple-est, but installing freetype requires more than 
> ./configure && make && sudo make install.
> Option 2 worries me with the manual symlinking and such. Who knows 
> what we'll clobber.
> Option 3: haven't fully explored.
> Option 4: This would require some input from whoever (Gohlke?, Owen?) 
> makes the binary installers.
>
>
> [1] http://www.libpng.org/pub/png/libpng.html
> [2] http://www.freetype.org/index.html
> [3] http://xquartz.macosforge.org/landing/
> [4] 
> http://www.astro.washington.edu/users/rowen/BuildingMatplotlibForMac.html
> [5] http://www.freedesktop.org/wiki/Software/pkg-config/
>
>
> On Thu, Aug 22, 2013 at 8:24 PM, Matt Terry <mat...@gm... 
> <mailto:mat...@gm...>> wrote:
>
>         > with/without third party X
>         I'm not quite sure what you mean by with/without third party
>         X. If you
>         are referring to Tck/Tk:
>
>
>     I had an issue where MPL found the headers to freetype in
>     /opt/local, but library in /usr/X11. Hilarity ensues.  I *think*
>     /usr/X11 showed up when I installed XQuartz, but I don't have a
>     clean image to compare against.
>
>     The with-X / without-X builds would be there to check that the
>     default search paths are compatible with common environments.
>
>     -matt
>
>
>
>
> ------------------------------------------------------------------------------
> Introducing Performance Central, a new site from SourceForge and
> AppDynamics. Performance Central is your source for news, insights,
> analysis and resources for efficient Application Performance Management.
> Visit us today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

On Fri, Aug 23, 2013 at 11:21 AM, Russell Owen <ro...@uw...> wrote:
> Here are my old instructions (I deleted them when I started using Apple's libraries, but the wayback machine saves the day):

Thanks Russell -- this is helpful. A few comments:

>         • If you plan to redistribute matplotlib, delete (or temporarily move) the dynamic library so matplotlib statically links to libpng:
> % sudo rm /usr/local/lib/libpng*.dylib

I've found that passing --disable-shared works to prevent the dylibs
from being built at all. At least with libpng.

>         • To check if a library is universal, run "file" on it, e.g.:
> % file /usr/local/lib/libpng*.a

this doesn't work for me on *.a files -- though it does on dylibs

>         • Before building, you may wish to modify include/freetype/configure/ftoption.h to enable hinting:
>                 • uncomment: #define TT_CONFIG_OPTION_BYTECODE_INTERPRETER
>                 • perhaps comment out: #define TT_CONFIG_OPTION_UNPATENTED_HINTING

handy to know.

Thanks,

-Chris


-- 

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

Chr...@no...

On Fri, Aug 23, 2013 at 8:14 AM, Matt Terry <mat...@gm...> wrote:
> I'm banging away at installing MPL on top of python.org's python.

This is why binary installers are good idea!

> the libfreetype/freetype issue.

yeah, that's kind of ugly....and where is doesn't "just work" for me...

> 1) install libpng[1] and freetype[2] from source

libpng and freetype are different, though install from source may be
the way to go:

libpng is there, but is not properly installed, I'm not sure it's got
the header for the same version as the lib, and libpng-config is
either not there or not for the right version or somethign ugly. It
look, form messages at build time, that someone has hacked some code
into the MPL build that figures all that out, but for other stuff I'm
doing, I just punt and build libpng -- that's pretty straighforward,
at least. But teh solution in the MPL code now seems to work.

> 2) install XQuartz[3] and twiddle /opt/X11, /usr/X11 (per Russell's
> directions[4]) so MPL finds XQuartz's libpng/freetype

I _think_ that OS-X now ships with X11, which has freetype (though
installed weirdly once again...) we certainly should NOT expect people
to install anything big to build MPL, and binaries should not depend
on anything not shipped by Apple by default.

According to Russell, you do need to install something, so I think that's out.

> 4) create the MPL binary installer and use that

That's what most people should do -- but one of us needs to build it.

> Option 1 seems simple-est, but installing freetype requires more than
> ./configure && make && sudo make install.

darn. But hopefully we can figure it out.

> Option 4: This would require some input from whoever (Gohlke?, Owen?) makes
> the binary installers.

I think Russell has been doing it for MPL lately.

My thoughts:

We want to support two user-bases:

1) folks that don't mind a little command line work, and probably need
other scientific libs, etc anyway, an want an MPL that runs on their
machine:
   - these folks should use homebrew or macports to build the
dependencies (or even hand-compile them). Ideally we have setup.py
that will find those libs, and test to see that the builds work once
in a while.

2) folks that "just want to use it" and/or want a binary they can
re-distribute via py2app, etc.
  - for these folks, we need to provide binaries. These binaries should:
   1) Match the python.org python builds. (probably only the Intel ones now...)
   2) statically link the non-sytem libs

This has been done for a while, off and on, most recently by Russell, AFAIK.

But this is not a problem unique to MPL. All sorts of python packages
need this, and only some of the package maintainers do it (well).
Also, a bunch of packages require the same dependencies (i.e. PIL and
MPL both need png and freetype)

So, rather than re-inventing the wheel over and over again, It would
be great to have a central repository where we can develop build
scripts, etc that share an infrustructure for building these binaries.

I've started one:

https://github.com/MacPython/mac-builds

there is not much there, only a couple things I'm working on at the
moment (netCDF4, which is of interest to scipy folks, and py_gd, which
is my own simple drawing lib, that no one else uses (yet?)

If anyone wants to join the project let me know -- if I know you from
your work with this community, I'll gladly add you.

I'm using the gattai build system:
(https://sourceforge.net/projects/gattai/). I decided to do that, as I
was sick of re-writing essentially the same build scripts, and I kept
adding features to mine that would have resulted in re-implementing
gattai anyway. I've been hacking at gattai, and its author is quite
open to moving it forward.

That being said, there is no reason that we need to use the same build
system -- we could easily have custom build scripts for a project, and
still have it share the dependencies.

I was planning on getting it all further along before announcing the
project and looking for help, but since is came up...

-Chris

-- 

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

Chr...@no...

On Aug 22, 2013, at 8:24 PM, Matt Terry <mat...@gm...> wrote:

> > with/without third party X
> I'm not quite sure what you mean by with/without third party X. If you
> are referring to Tck/Tk:
> 
> I had an issue where MPL found the headers to freetype in /opt/local, but library in /usr/X11.  Hilarity ensues.  I *think* /usr/X11 showed up when I installed XQuartz, but I don't have a clean image to compare against.
> 
> The with-X / without-X builds would be there to check that the default search paths are compatible with common environments.

Have you tried eliminating /opt from the search path in setupext.py? If that does the trick, I think we may be stuck. The default search paths are trying to work for default python, python.org python, macports and homebrew, plus user-built libraries in /usr/local. I'm not convinced one file can do it all. Apple moving X from /usr/X11 to /opt/X11 did not help.

Regards,

-- Russell

On Aug 23, 2013, at 8:14 AM, Matt Terry <mat...@gm...> wrote:

> I'm banging away at installing MPL on top of python.org's python.  I'm at the libfreetype/freetype issue.  There seems to be three approaches to getting MPL's dependencies.
> 
> 1) install libpng[1] and freetype[2] from source
> 2) install XQuartz[3] and twiddle /opt/X11, /usr/X11 (per Russell's directions[4]) so MPL finds XQuartz's libpng/freetype
> 3) install XQuartz[3] and install pkg-config[5] so MPL can find the cleverly installed libraries
> 4) create the MPL binary installer and use that
> 
> Option 1 seems simple-est, but installing freetype requires more than ./configure && make && sudo make install.
> Option 2 worries me with the manual symlinking and such.  Who knows what we'll clobber.
> Option 3: haven't fully explored.
> Option 4: This would require some input from whoever (Gohlke?, Owen?) makes the binary installers.
> 
> [1] http://www.libpng.org/pub/png/libpng.html
> [2] http://www.freetype.org/index.html
> [3] http://xquartz.macosforge.org/landing/
> [4] http://www.astro.washington.edu/users/rowen/BuildingMatplotlibForMac.html
> [5] http://www.freedesktop.org/wiki/Software/pkg-config/

I'm a bit puzzled what you are trying to do. I've found that matplotlib "just builds" if I only want to use it on the Mac I'm building it on. Depending on what you've added to your Mac you may find you have to restrict the search dirs in setupext.py, but that's all I have ever had to do for years.

For me the problems arise when trying to build a binary installer that runs on multiple versions of MacOS.

The following comments all deal with that case (making a binary installer):

I would eliminate (2) as an option; I thought it would help but it doesn't (perhaps I need to update my matplotlib build instructions). The issue is that when I build a binary installer on 10.8, it cannot be used on 10.6 because it is looking for some libraries in /opt/X11 (which is where XQuartz is installed on 10.8) instead of /usr/X11 (which is where X11 is installed on 10.6). It's only an issue for binary installers; I haven't had any problem just building matplotlib for python.org python.

I have pretty much given up building binary installers on anything but the oldest version of MacOS X that they can be used on (or as close as I can get). I've just run into too many problems like this.

I like (1) for binary installers. It eliminates the need for a user to have installed X11 at all. The hassle is making sure matplotlib statically links these libraries. I've always done this by taking the crude approach of deleting the shared object libraries, leaving only the static libraries; it always worked in the past, but recently I ran into a problem where something I was building simply refused to use a static library (I don't remember the details).

Regarding option [4]. You can get a binary installer for matplotlib 1.3 from here:
<http://www.astro.washington.edu/users/rowen/python/>
but it may clobber your python-dateutil and pytz (especially likely if they were installed by the matplotlib 1.2.1 binary installer). That's the main reason it's not an official binary installer.

-- Russell

I'm banging away at installing MPL on top of python.org's python.  I'm at
the libfreetype/freetype issue.  There seems to be three approaches to
getting MPL's dependencies.

1) install libpng[1] and freetype[2] from source
2) install XQuartz[3] and twiddle /opt/X11, /usr/X11 (per Russell's
directions[4]) so MPL finds XQuartz's libpng/freetype
3) install XQuartz[3] and install pkg-config[5] so MPL can find the
cleverly installed libraries
4) create the MPL binary installer and use that

Option 1 seems simple-est, but installing freetype requires more than
./configure && make && sudo make install.
Option 2 worries me with the manual symlinking and such.  Who knows what
we'll clobber.
Option 3: haven't fully explored.
Option 4: This would require some input from whoever (Gohlke?, Owen?) makes
the binary installers.


[1] http://www.libpng.org/pub/png/libpng.html
[2] http://www.freetype.org/index.html
[3] http://xquartz.macosforge.org/landing/
[4]
http://www.astro.washington.edu/users/rowen/BuildingMatplotlibForMac.html
[5] http://www.freedesktop.org/wiki/Software/pkg-config/


On Thu, Aug 22, 2013 at 8:24 PM, Matt Terry <mat...@gm...> wrote:

>  > with/without third party X
>> I'm not quite sure what you mean by with/without third party X. If you
>> are referring to Tck/Tk:
>>
>
> I had an issue where MPL found the headers to freetype in /opt/local, but
> library in /usr/X11.  Hilarity ensues.  I *think* /usr/X11 showed up when I
> installed XQuartz, but I don't have a clean image to compare against.
>
> The with-X / without-X builds would be there to check that the default
> search paths are compatible with common environments.
>
> -matt
>

>
> > with/without third party X
> I'm not quite sure what you mean by with/without third party X. If you
> are referring to Tck/Tk:
>

I had an issue where MPL found the headers to freetype in /opt/local, but
library in /usr/X11.  Hilarity ensues.  I *think* /usr/X11 showed up when I
installed XQuartz, but I don't have a clean image to compare against.

The with-X / without-X builds would be there to check that the default
search paths are compatible with common environments.

-matt

In article 
<CAK...@ma...>,
 Matt Terry <mat...@gm...> wrote:

> That is handy information.  I'll start adding a python.org target.
> 
> How broad coverage do we want?
> 10.6, 10.7, 10.8
> system, python.org (2.7, 3.3), brew, macports
> virtualenv, no virtualenv
> with/without third party X
> 
> The testing matrix blows up pretty quickly.  For those of you with longer
> memories, where are the corners where things tend to break?

That list looks reasonable to me, and I'm not sure how to whittle it 
down, and it may need to grow. MacOS X 10.9 will be out soon and you may 
also want to include fink. 

I'm not quite sure what you mean by with/without third party X. If you 
are referring to Tck/Tk:
- For Apple's python: I suggest testing both the built-in Tcl/TK and (if 
you can) ActiveState Tcl/Tk, since anyone who really cares about Tcl/Tk 
will probably not use the one provided by Apple (at least that was true 
in older versions of MacOS X; I can't speak for 10.8).
- For python.org I think you only need to test with ActiveState Tcl/Tk.
- for homebrew, macports and fink, I'm not sure how many choices you 
have; just one X11-based and one Aqua-based Tcl/Tk (if both are even 
available)?

-- Russell

> 
> -matt
> 
> 
> 
> On Tue, Aug 20, 2013 at 12:09 PM, Russell E. Owen 
> <ro...@uw...> wrote:
> 
> > A few hints:
> >
> > If you just want to build matplotlib for your own computer (and don't
> > care about making an installer that will work on anybody else's) then
> > you can install from source with very little trouble:
> > - You may want to edit setupext.py to limit searching to those dirs that
> > really matter, but this is only needed if you have installed extras that
> > might conflict.
> > - You may want to edit setup.cfg to select a better default back end.
> >
> > You have to be much more careful if you want to build a binary installer
> > that can be used by others. I've found that bdist_mpkg works, and I've
> > found it is safest to build on the oldest platform I want the installer
> > to support (for example /usr/X11/lib moved in 10.8 or 10.7 in a way that
> > is forward but not backwards compatible).
> >
> > For Apple's python you need install anything; all you need is in
> > /usr/lib and /usr/X11/lib. I have no idea if TkAgg works well.
> >
> > For python.org python you should install a version of Tcl/Tk. I suggest
> > ActiveState Tcl/Tk 8.5.11. Be warned that versions 8.5.12, 8.5.12.1,
> > 8.5.13 all have known crashing problems; I have not tried 8.5.14 (which
> > came out fairly recently) as 8.5.11 seems to do well enough.
> >
> > I've cannot comment on building matplotlib for macports, fink or
> > homebrew.
> >
> > -- Russell
> >
> > In article <520...@st...>,
> >  Michael Droettboom <md...@st...>
> >  wrote:
> >
> > > We actually discussed this very issue yesterday in our Google hangout
> > > about continuous integration. We're probably going to need to script a
> > > full setup from a clean Mac + XCode to a working matplotlib development
> > > environment in order to make that happen, and obviously that will be
> > > shared with the world.  Things are even more complex on Windows, and I'd
> > > like to do that there, too.  So stay tuned.
> > >
> > > Mike
> > >
> > > On 08/16/2013 10:02 AM, Paul Hobson wrote:
> > > > Mike,
> > > >
> > > > That's great news. Is there any chance we can look forward to
> > > > "official" instructions for setting up a Mac to develop matplotlib?
> > > >
> > > > I gave up a long time ago and started piecing to together my meager
> > > > PRs in a linux VM.
> > > > -paul
> > > >
> > > >
> > > > On Fri, Aug 16, 2013 at 6:52 AM, Michael Droettboom
> > > > <md...@st...
> > > > <mailto:md...@st...>> wrote:
> > > >
> > > >     Thanks to the gracious donation from Hans Petter Langtangen and the
> > > >     Center for Biomedical Computing at Simula
> > > >     (http://home.simula.no/~hpl <http://home.simula.no/%7Ehpl>),
> > > >     I now have a new Mac Mini sitting at my desk.  This should allow
> > me to
> > > >     keep on top of changes that affect the Mac builds and to better
> > track
> > > >     down Mac-only issues.
> > > >
> > > >     Stay tuned over the next few weeks and months as we will most
> > > >     likely be
> > > >     using some more of these funds to pay for hosted continuous
> > > >     integration
> > > >     services (as discussed yesterday in our MEP19 Google Hangout).
> > > >
> > > >     Cheers,
> > > >     Mike
> >
> >
> >
> > ----------------------------------------------------------------------------
> > --
> > Introducing Performance Central, a new site from SourceForge and
> > AppDynamics. Performance Central is your source for news, insights,
> > analysis and resources for efficient Application Performance Management.
> > Visit us today!
> > http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
> > _______________________________________________
> > Matplotlib-devel mailing list
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> >
> ---------------------------------------------------------------------
> ------------------------------------------------------------------------------
> Introducing Performance Central, a new site from SourceForge and 
> AppDynamics. Performance Central is your source for news, insights, 
> analysis and resources for efficient Application Performance Management. 
> Visit us today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk---
> ------------------------------------------------------------------
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

That is handy information.  I'll start adding a python.org target.

How broad coverage do we want?
10.6, 10.7, 10.8
system, python.org (2.7, 3.3), brew, macports
virtualenv, no virtualenv
with/without third party X

The testing matrix blows up pretty quickly.  For those of you with longer
memories, where are the corners where things tend to break?

-matt



On Tue, Aug 20, 2013 at 12:09 PM, Russell E. Owen <ro...@uw...> wrote:

> A few hints:
>
> If you just want to build matplotlib for your own computer (and don't
> care about making an installer that will work on anybody else's) then
> you can install from source with very little trouble:
> - You may want to edit setupext.py to limit searching to those dirs that
> really matter, but this is only needed if you have installed extras that
> might conflict.
> - You may want to edit setup.cfg to select a better default back end.
>
> You have to be much more careful if you want to build a binary installer
> that can be used by others. I've found that bdist_mpkg works, and I've
> found it is safest to build on the oldest platform I want the installer
> to support (for example /usr/X11/lib moved in 10.8 or 10.7 in a way that
> is forward but not backwards compatible).
>
> For Apple's python you need install anything; all you need is in
> /usr/lib and /usr/X11/lib. I have no idea if TkAgg works well.
>
> For python.org python you should install a version of Tcl/Tk. I suggest
> ActiveState Tcl/Tk 8.5.11. Be warned that versions 8.5.12, 8.5.12.1,
> 8.5.13 all have known crashing problems; I have not tried 8.5.14 (which
> came out fairly recently) as 8.5.11 seems to do well enough.
>
> I've cannot comment on building matplotlib for macports, fink or
> homebrew.
>
> -- Russell
>
> In article <520...@st...>,
>  Michael Droettboom <md...@st...>
>  wrote:
>
> > We actually discussed this very issue yesterday in our Google hangout
> > about continuous integration. We're probably going to need to script a
> > full setup from a clean Mac + XCode to a working matplotlib development
> > environment in order to make that happen, and obviously that will be
> > shared with the world.  Things are even more complex on Windows, and I'd
> > like to do that there, too.  So stay tuned.
> >
> > Mike
> >
> > On 08/16/2013 10:02 AM, Paul Hobson wrote:
> > > Mike,
> > >
> > > That's great news. Is there any chance we can look forward to
> > > "official" instructions for setting up a Mac to develop matplotlib?
> > >
> > > I gave up a long time ago and started piecing to together my meager
> > > PRs in a linux VM.
> > > -paul
> > >
> > >
> > > On Fri, Aug 16, 2013 at 6:52 AM, Michael Droettboom
> > > <md...@st...
> > > <mailto:md...@st...>> wrote:
> > >
> > >     Thanks to the gracious donation from Hans Petter Langtangen and the
> > >     Center for Biomedical Computing at Simula
> > >     (http://home.simula.no/~hpl <http://home.simula.no/%7Ehpl>),
> > >     I now have a new Mac Mini sitting at my desk.  This should allow
> me to
> > >     keep on top of changes that affect the Mac builds and to better
> track
> > >     down Mac-only issues.
> > >
> > >     Stay tuned over the next few weeks and months as we will most
> > >     likely be
> > >     using some more of these funds to pay for hosted continuous
> > >     integration
> > >     services (as discussed yesterday in our MEP19 Google Hangout).
> > >
> > >     Cheers,
> > >     Mike
>
>
>
> ------------------------------------------------------------------------------
> Introducing Performance Central, a new site from SourceForge and
> AppDynamics. Performance Central is your source for news, insights,
> analysis and resources for efficient Application Performance Management.
> Visit us today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

A few hints:

If you just want to build matplotlib for your own computer (and don't 
care about making an installer that will work on anybody else's) then 
you can install from source with very little trouble:
- You may want to edit setupext.py to limit searching to those dirs that 
really matter, but this is only needed if you have installed extras that 
might conflict.
- You may want to edit setup.cfg to select a better default back end.

You have to be much more careful if you want to build a binary installer 
that can be used by others. I've found that bdist_mpkg works, and I've 
found it is safest to build on the oldest platform I want the installer 
to support (for example /usr/X11/lib moved in 10.8 or 10.7 in a way that 
is forward but not backwards compatible).

For Apple's python you need install anything; all you need is in 
/usr/lib and /usr/X11/lib. I have no idea if TkAgg works well.

For python.org python you should install a version of Tcl/Tk. I suggest 
ActiveState Tcl/Tk 8.5.11. Be warned that versions 8.5.12, 8.5.12.1, 
8.5.13 all have known crashing problems; I have not tried 8.5.14 (which 
came out fairly recently) as 8.5.11 seems to do well enough.

I've cannot comment on building matplotlib for macports, fink or 
homebrew.

-- Russell

In article <520...@st...>,
 Michael Droettboom <md...@st...> 
 wrote:

> We actually discussed this very issue yesterday in our Google hangout 
> about continuous integration. We're probably going to need to script a 
> full setup from a clean Mac + XCode to a working matplotlib development 
> environment in order to make that happen, and obviously that will be 
> shared with the world.  Things are even more complex on Windows, and I'd 
> like to do that there, too.  So stay tuned.
> 
> Mike
> 
> On 08/16/2013 10:02 AM, Paul Hobson wrote:
> > Mike,
> >
> > That's great news. Is there any chance we can look forward to 
> > "official" instructions for setting up a Mac to develop matplotlib?
> >
> > I gave up a long time ago and started piecing to together my meager 
> > PRs in a linux VM.
> > -paul
> >
> >
> > On Fri, Aug 16, 2013 at 6:52 AM, Michael Droettboom 
> > <md...@st... 
> > <mailto:md...@st...>> wrote:
> >
> >     Thanks to the gracious donation from Hans Petter Langtangen and the
> >     Center for Biomedical Computing at Simula
> >     (http://home.simula.no/~hpl <http://home.simula.no/%7Ehpl>),
> >     I now have a new Mac Mini sitting at my desk.  This should allow me to
> >     keep on top of changes that affect the Mac builds and to better track
> >     down Mac-only issues.
> >
> >     Stay tuned over the next few weeks and months as we will most
> >     likely be
> >     using some more of these funds to pay for hosted continuous
> >     integration
> >     services (as discussed yesterday in our MEP19 Google Hangout).
> >
> >     Cheers,
> >     Mike

On Fri, Aug 16, 2013 at 3:41 PM, Hubert Holin <Hub...@fr...> wrote:
>                 Building for various architectures than one is on, on the Mac, is something I regretfully bought into (Apple in the beginning told us to go for it) but latter found out to be a useless hassle (Apple silently removing PPC64 dev tools anybody? Urgh!)
>
>         Bon courage

merci.

and I've felt your frustration, but it is setting down -- I know I
finally got rid of my old Mac G5 (nice machine to the end...), and I
think we can simply stick with Intel32+64 bit now, so not as bad.

And I do think there a real benefit to being about to provide
newbie-friendly option that "just works" on the Mac.

-Chris


-- 

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

Chr...@no...

It would be nice to have mpl tested on a few different environments.  The
obvious ones are:

clean macos
macos + brew (py2/py3)
macos + macports (2.6, 2.7, (3.1?), 3.2, 3.3)

I started a repo to install these environments on travis CI's mac
environment.  I don't have all the bugs shaken out of the macports
environments, but it may be a useful starting place for standardizing
installation instructions.

https://github.com/mrterry/mpl_on_travis_mac


On Fri, Aug 16, 2013 at 3:45 PM, Hubert Holin <Hub...@fr...> wrote:

> Paris (U.E.), le 17/08/2013
>
> Bonsoir
>
> Pandas does compile on a plain Mac (I use it at work), though I have not
> pulled since may the 22nd, so things may have changed.
>
> Bon courage
>
> Hubert Holin
>
>
> On 16 août 2013, at 18:27, Paul Hobson <pmh...@gm...> wrote:
>
>
>
>
> On Fri, Aug 16, 2013 at 7:42 AM, Jens Nielsen <jen...@gm...>wrote:
>
>> On my mac box I'm just using homebrew www.brew.sh to install the latest
>> python along with all non python dependencies and the python dependencies
>> via pip. This seems to work great most of the time.
>> Jens
>>
>>
> Yeah. I'm sure Homebrew has made a lot of progress since I last tried. A
> couple of years ago I found a couple of blog posts that all walked you
> through different ways of getting a dev environment going for the various
> flavors of python installed (it was never /all/ available through
> Homebrew). Sometimes one would work for me. Eventually I just said, "screw
> it" and installed Anaconda for use and fired up a VM for development.
>
> I guess my point is that it'd be nice to have documentation on
> matplotlib.org that says, "Here's how Mike D. sets up his Mac to build
> mpl from source". Because if it works well enough for Mike, it'll probably
> work well enough for me. (Now if only pandas would do the same thing.)
>
> A similar document would be great for Windows too.
> -paul
>
>
>
>>  On Fri, Aug 16, 2013 at 3:32 PM, Michael Droettboom <md...@st...>wrote:
>>
>>>  We actually discussed this very issue yesterday in our Google hangout
>>> about continuous integration.  We're probably going to need to script a
>>> full setup from a clean Mac + XCode to a working matplotlib development
>>> environment in order to make that happen, and obviously that will be shared
>>> with the world.  Things are even more complex on Windows, and I'd like to
>>> do that there, too.  So stay tuned.
>>>
>>> Mike
>>>
>>>
>>> On 08/16/2013 10:02 AM, Paul Hobson wrote:
>>>
>>> Mike,
>>>
>>>  That's great news. Is there any chance we can look forward to
>>> "official" instructions for setting up a Mac to develop matplotlib?
>>>
>>>  I gave up a long time ago and started piecing to together my meager
>>> PRs in a linux VM.
>>> -paul
>>>
>>>
>>> On Fri, Aug 16, 2013 at 6:52 AM, Michael Droettboom <md...@st...>wrote:
>>>
>>>> Thanks to the gracious donation from Hans Petter Langtangen and the
>>>> Center for Biomedical Computing at Simula (http://home.simula.no/~hpl),
>>>> I now have a new Mac Mini sitting at my desk.  This should allow me to
>>>> keep on top of changes that affect the Mac builds and to better track
>>>> down Mac-only issues.
>>>>
>>>> Stay tuned over the next few weeks and months as we will most likely be
>>>> using some more of these funds to pay for hosted continuous integration
>>>> services (as discussed yesterday in our MEP19 Google Hangout).
>>>>
>>>> Cheers,
>>>> Mike
>>>>
>>>
>>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk_______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>

Paris (U.E.), le 17/08/2013

	Bonsoir

		Pandas does compile on a plain Mac (I use it at work), though I have not pulled since may the 22nd, so things may have changed.

	Bon courage

			Hubert Holin


On 16 août 2013, at 18:27, Paul Hobson <pmh...@gm...> wrote:

> 
> 
> 
> On Fri, Aug 16, 2013 at 7:42 AM, Jens Nielsen <jen...@gm...> wrote:
> On my mac box I'm just using homebrew www.brew.sh to install the latest python along with all non python dependencies and the python dependencies via pip. This seems to work great most of the time. 
> 
> Jens
> 
> 
> Yeah. I'm sure Homebrew has made a lot of progress since I last tried. A couple of years ago I found a couple of blog posts that all walked you through different ways of getting a dev environment going for the various flavors of python installed (it was never /all/ available through Homebrew). Sometimes one would work for me. Eventually I just said, "screw it" and installed Anaconda for use and fired up a VM for development.
> 
> I guess my point is that it'd be nice to have documentation on matplotlib.org that says, "Here's how Mike D. sets up his Mac to build mpl from source". Because if it works well enough for Mike, it'll probably work well enough for me. (Now if only pandas would do the same thing.)
> 
> A similar document would be great for Windows too.
> -paul
> 
>  
> On Fri, Aug 16, 2013 at 3:32 PM, Michael Droettboom <md...@st...> wrote:
> We actually discussed this very issue yesterday in our Google hangout about continuous integration.  We're probably going to need to script a full setup from a clean Mac + XCode to a working matplotlib development environment in order to make that happen, and obviously that will be shared with the world.  Things are even more complex on Windows, and I'd like to do that there, too.  So stay tuned.
> 
> Mike
> 
> 
> On 08/16/2013 10:02 AM, Paul Hobson wrote:
>> Mike,
>> 
>> That's great news. Is there any chance we can look forward to "official" instructions for setting up a Mac to develop matplotlib?
>> 
>> I gave up a long time ago and started piecing to together my meager PRs in a linux VM.
>> -paul
>> 
>> 
>> On Fri, Aug 16, 2013 at 6:52 AM, Michael Droettboom <md...@st...> wrote:
>> Thanks to the gracious donation from Hans Petter Langtangen and the
>> Center for Biomedical Computing at Simula (http://home.simula.no/~hpl),
>> I now have a new Mac Mini sitting at my desk.  This should allow me to
>> keep on top of changes that affect the Mac builds and to better track
>> down Mac-only issues.
>> 
>> Stay tuned over the next few weeks and months as we will most likely be
>> using some more of these funds to pay for hosted continuous integration
>> services (as discussed yesterday in our MEP19 Google Hangout).
>> 
>> Cheers,
>> Mike
> 
> 
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead. 
> Download for free and get started troubleshooting in minutes. 
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk_______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Paris (U.E.), le 17/08/2013

	Bonsoir

		Building for various architectures than one is on, on the Mac, is something I regretfully bought into (Apple in the beginning told us to go for it) but latter found out to be a useless hassle (Apple silently removing PPC64 dev tools anybody? Urgh!)

	Bon courage

			Hubert Holin


On 16 août 2013, at 18:08, Chris Barker - NOAA Federal <chr...@no...> wrote:

> On Fri, Aug 16, 2013 at 7:32 AM, Michael Droettboom <md...@st...> wrote:
>> We actually discussed this very issue yesterday in our Google hangout about
>> continuous integration.  We're probably going to need to script a full setup
>> from a clean Mac + XCode to a working matplotlib development environment in
>> order to make that happen,
> 
> Just a note -- this did NOT "just work" the other day for me -- it
> found the freetype libs that OS-X has in the X11 build, but didn't
> like them at compile time. I haven't debugged it yet, sorry.
> 
> But the real trick here is what you want to build: which OS-X versions
> do you want to support? which architectures? which Python Build(s)?
> 
> What I've been planning on doing is setting up a gitHub (or something)
> project for building the various dependencies that various python
> packages need -- there are a few that are broadly used: libpng,
> libfreetype (used by MPL, PIL, wxPython, ???). The idea is that if you
> wanted to build MPL (or PIL, or ???) you'd grab the
> MacPyton_Dependencies project, build it, then go from there.
> 
> Anyone want to help? It just feels like we are all repeating
> each-others work a LOT here!
> 
> NOTE: the big issues come up if you want to build binaries that are
> re-distributable (as a package, or with py2app, or???). In this case,
> you need binaries that can run on perhaps older machines than the one
> you're building on, or a different architecture. Building to run on
> the machine it's built-on is a lot easier. (particularly with macport
> or homebrew)
> 
> -CHB
> 
> 
> 
> 
> 
> 
> 
> 
> and obviously that will be shared with the world.
>> Things are even more complex on Windows, and I'd like to do that there, too.
>> So stay tuned.
>> 
>> Mike
>> 
>> 
>> On 08/16/2013 10:02 AM, Paul Hobson wrote:
>> 
>> Mike,
>> 
>> That's great news. Is there any chance we can look forward to "official"
>> instructions for setting up a Mac to develop matplotlib?
>> 
>> I gave up a long time ago and started piecing to together my meager PRs in a
>> linux VM.
>> -paul
>> 
>> 
>> On Fri, Aug 16, 2013 at 6:52 AM, Michael Droettboom <md...@st...> wrote:
>>> 
>>> Thanks to the gracious donation from Hans Petter Langtangen and the
>>> Center for Biomedical Computing at Simula (http://home.simula.no/~hpl),
>>> I now have a new Mac Mini sitting at my desk.  This should allow me to
>>> keep on top of changes that affect the Mac builds and to better track
>>> down Mac-only issues.
>>> 
>>> Stay tuned over the next few weeks and months as we will most likely be
>>> using some more of these funds to pay for hosted continuous integration
>>> services (as discussed yesterday in our MEP19 Google Hangout).
>>> 
>>> Cheers,
>>> Mike
>>> 
>>> 
>>> 
>>> 
>>> ------------------------------------------------------------------------------
>>> Get 100% visibility into Java/.NET code with AppDynamics Lite!
>>> It's a free troubleshooting tool designed for production.
>>> Get down to code-level detail for bottlenecks, with <2% overhead.
>>> Download for free and get started troubleshooting in minutes.
>>> 
>>> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Matplotlib-devel mailing list
>>> Mat...@li...
>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>> 
>> 
>> 
>> 
>> ------------------------------------------------------------------------------
>> Get 100% visibility into Java/.NET code with AppDynamics Lite!
>> It's a free troubleshooting tool designed for production.
>> Get down to code-level detail for bottlenecks, with <2% overhead.
>> Download for free and get started troubleshooting in minutes.
>> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>> 
> 
> 
> 
> -- 
> 
> 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
> 
> Chr...@no...
> 
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead. 
> Download for free and get started troubleshooting in minutes. 
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Paris (U.E.), le 17/08/2013

	Bonsoir

		Both on my old (PPC) Mac at work and on my (somewhat) more recent (Intel) Mac at home, I install from source (no homebrew, Fink, MacPorts or whatever, though these are great to-have items!): latest stable release for Python itself (2.7 & 3.3), the rest from repositories. I guess I am lucky not to have run into a wall, or perhaps just plain stubborn… There is perhaps a lack of functionality (I have not delved into IPython notebooks, and Tcl/Tk usually is a nightmare for my old box), but for what I have, or want, to do, it just works. I should add that at work I am behind a really "thick" firewall, so I pay close attention to all dependencies and install these before what depends on them (obviously!, though there are (partly) circular references which require more work); I do sometimes have to download at home and transfer via key…

		At any rate, a well-documented (I just whent ahead and kept no notes… sorry!) installation roadmap would really be a usefull thing.

	And thanks for the great woks which goes into matplotlib (it really made my life more bearable)!

			Hubert Holin


On 16 août 2013, at 16:42, Jens Nielsen <jen...@gm...> wrote:

> On my mac box I'm just using homebrew www.brew.sh to install the latest python along with all non python dependencies and the python dependencies via pip. This seems to work great most of the time. 
> 
> Jens
> 
> 
> On Fri, Aug 16, 2013 at 3:32 PM, Michael Droettboom <md...@st...> wrote:
> We actually discussed this very issue yesterday in our Google hangout about continuous integration.  We're probably going to need to script a full setup from a clean Mac + XCode to a working matplotlib development environment in order to make that happen, and obviously that will be shared with the world.  Things are even more complex on Windows, and I'd like to do that there, too.  So stay tuned.
> 
> Mike
> 
> 
> On 08/16/2013 10:02 AM, Paul Hobson wrote:
>> Mike,
>> 
>> That's great news. Is there any chance we can look forward to "official" instructions for setting up a Mac to develop matplotlib?
>> 
>> I gave up a long time ago and started piecing to together my meager PRs in a linux VM.
>> -paul
>> 
>> 
>> On Fri, Aug 16, 2013 at 6:52 AM, Michael Droettboom <md...@st...> wrote:
>> Thanks to the gracious donation from Hans Petter Langtangen and the
>> Center for Biomedical Computing at Simula (http://home.simula.no/~hpl),
>> I now have a new Mac Mini sitting at my desk.  This should allow me to
>> keep on top of changes that affect the Mac builds and to better track
>> down Mac-only issues.
>> 
>> Stay tuned over the next few weeks and months as we will most likely be
>> using some more of these funds to pay for hosted continuous integration
>> services (as discussed yesterday in our MEP19 Google Hangout).
>> 
>> Cheers,
>> Mike
>> 
>> 
>> 
>> ------------------------------------------------------------------------------
>> Get 100% visibility into Java/.NET code with AppDynamics Lite!
>> It's a free troubleshooting tool designed for production.
>> Get down to code-level detail for bottlenecks, with <2% overhead.
>> Download for free and get started troubleshooting in minutes.
>> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>> 
> 
> 
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> 
> 
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead. 
> Download for free and get started troubleshooting in minutes. 
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk_______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

On Fri, Aug 16, 2013 at 9:08 AM, Chris Barker - NOAA Federal <
chr...@no...> wrote:

> On Fri, Aug 16, 2013 at 7:32 AM, Michael Droettboom <md...@st...>
> wrote:
> > We actually discussed this very issue yesterday in our Google hangout
> about
> > continuous integration.  We're probably going to need to script a full
> setup
> > from a clean Mac + XCode to a working matplotlib development environment
> in
> > order to make that happen,
>
> Just a note -- this did NOT "just work" the other day for me -- it
> found the freetype libs that OS-X has in the X11 build, but didn't
> like them at compile time. I haven't debugged it yet, sorry.
>
> But the real trick here is what you want to build: which OS-X versions
> do you want to support? which architectures? which Python Build(s)?
>
> What I've been planning on doing is setting up a gitHub (or something)
> project for building the various dependencies that various python
> packages need -- there are a few that are broadly used: libpng,
> libfreetype (used by MPL, PIL, wxPython, ???). The idea is that if you
> wanted to build MPL (or PIL, or ???) you'd grab the
> MacPyton_Dependencies project, build it, then go from there.
>
> Anyone want to help? It just feels like we are all repeating
> each-others work a LOT here!
>
> NOTE: the big issues come up if you want to build binaries that are
> re-distributable (as a package, or with py2app, or???). In this case,
> you need binaries that can run on perhaps older machines than the one
> you're building on, or a different architecture. Building to run on
> the machine it's built-on is a lot easier. (particularly with macport
> or homebrew)
>
> -CHB


Wow! Ambitious. I'll try to keep track of this and help out where possible.

Side note: it'll probably be good to alert the pandas folks to such a
project. I feel like they're always on Macs at their presentations. They
probably have some good ideas for this stuff.
-p

On Fri, Aug 16, 2013 at 7:42 AM, Jens Nielsen <jen...@gm...>wrote:

> On my mac box I'm just using homebrew www.brew.sh to install the latest
> python along with all non python dependencies and the python dependencies
> via pip. This seems to work great most of the time.
> Jens
>
>
Yeah. I'm sure Homebrew has made a lot of progress since I last tried. A
couple of years ago I found a couple of blog posts that all walked you
through different ways of getting a dev environment going for the various
flavors of python installed (it was never /all/ available through
Homebrew). Sometimes one would work for me. Eventually I just said, "screw
it" and installed Anaconda for use and fired up a VM for development.

I guess my point is that it'd be nice to have documentation on
matplotlib.org that says, "Here's how Mike D. sets up his Mac to build mpl
from source". Because if it works well enough for Mike, it'll probably work
well enough for me. (Now if only pandas would do the same thing.)

A similar document would be great for Windows too.
-paul



> On Fri, Aug 16, 2013 at 3:32 PM, Michael Droettboom <md...@st...>wrote:
>
>>  We actually discussed this very issue yesterday in our Google hangout
>> about continuous integration.  We're probably going to need to script a
>> full setup from a clean Mac + XCode to a working matplotlib development
>> environment in order to make that happen, and obviously that will be shared
>> with the world.  Things are even more complex on Windows, and I'd like to
>> do that there, too.  So stay tuned.
>>
>> Mike
>>
>>
>> On 08/16/2013 10:02 AM, Paul Hobson wrote:
>>
>> Mike,
>>
>>  That's great news. Is there any chance we can look forward to
>> "official" instructions for setting up a Mac to develop matplotlib?
>>
>>  I gave up a long time ago and started piecing to together my meager PRs
>> in a linux VM.
>> -paul
>>
>>
>> On Fri, Aug 16, 2013 at 6:52 AM, Michael Droettboom <md...@st...>wrote:
>>
>>> Thanks to the gracious donation from Hans Petter Langtangen and the
>>> Center for Biomedical Computing at Simula (http://home.simula.no/~hpl),
>>> I now have a new Mac Mini sitting at my desk.  This should allow me to
>>> keep on top of changes that affect the Mac builds and to better track
>>> down Mac-only issues.
>>>
>>> Stay tuned over the next few weeks and months as we will most likely be
>>> using some more of these funds to pay for hosted continuous integration
>>> services (as discussed yesterday in our MEP19 Google Hangout).
>>>
>>> Cheers,
>>> Mike
>>>
>>
>