I have a Mac!

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

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 <mdroe@…31…> 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

Matplotlib-devel@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

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 <mdroe@…31… > <mailto:mdroe@…31…>> 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/~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
    Matplotlib-devel@lists.sourceforge.net
    <mailto:Matplotlib-devel@lists.sourceforge.net>
    https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

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 <mdroe@…31…> 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


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

Matplotlib-devel@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

      On Fri, Aug 16, 2013 at 6:52 AM,

Michael Droettboom <mdroe@…31…> 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

        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](http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk)

        _______________________________________________

        Matplotlib-devel mailing list

        Matplotlib-devel@lists.sourceforge.net

        [https://lists.sourceforge.net/lists/listinfo/matplotlib-devel](https://lists.sourceforge.net/lists/listinfo/matplotlib-devel)

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.

···

On Fri, Aug 16, 2013 at 7:32 AM, Michael Droettboom <mdroe@...31...> wrote:

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 <mdroe@...31...> 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
Matplotlib-devel@lists.sourceforge.net
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
Matplotlib-devel@lists.sourceforge.net
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

Chris.Barker@...236...

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 7:42 AM, Jens Nielsen <jenshnielsen@...149...>wrote:

On Fri, Aug 16, 2013 at 3:32 PM, Michael Droettboom <mdroe@...31...>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 <mdroe@...31...>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

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 9:08 AM, Chris Barker - NOAA Federal < chris.barker@...236...> wrote:

On Fri, Aug 16, 2013 at 7:32 AM, Michael Droettboom <mdroe@...31...> > 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

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 Fri, Aug 16, 2013 at 3:32 PM, Michael Droettboom <mdroe@…31…> 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


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

Matplotlib-devel@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

      On Fri, Aug 16, 2013 at 6:52 AM,

Michael Droettboom <mdroe@…31…> 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

        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](http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk)

        _______________________________________________

        Matplotlib-devel mailing list

        Matplotlib-devel@lists.sourceforge.net

        [https://lists.sourceforge.net/lists/listinfo/matplotlib-devel](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 <chris.barker@...706...36...> wrote:

On Fri, Aug 16, 2013 at 7:32 AM, Michael Droettboom <mdroe@...31...> 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 <mdroe@...31...> 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
Matplotlib-devel@lists.sourceforge.net
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
Matplotlib-devel@lists.sourceforge.net
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

Chris.Barker@...236...

------------------------------------------------------------------------------
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
Matplotlib-devel@lists.sourceforge.net
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 Fri, Aug 16, 2013 at 7:42 AM, Jens Nielsen <jenshnielsen@…149…> 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 <mdroe@…31…> 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 <mdroe@…31…> 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

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 <Hubert.Holin@…207…> 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 <pmhobson@…149…> wrote:


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
Matplotlib-devel@lists.sourceforge.net
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

Matplotlib-devel@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

On Fri, Aug 16, 2013 at 7:42 AM, Jens Nielsen <jenshnielsen@…55…149…> 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 <mdroe@…31…> 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 <mdroe@…31…> 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

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

···

On Fri, Aug 16, 2013 at 3:41 PM, Hubert Holin <Hubert.Holin@...207...> 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

--

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.Barker@...236...