Text of discourse.matplotlib.org › t › calling-all-mac-osx-users › 15812 as Styx crawled it on Nov 19, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

Calling all Mac OSX users! - matplotlib-devel - Matplotlib

Calling all Mac OSX users! Development matplotlib-devel _Russell_E_Owen4 August 17, 2011, 6:45pm 1 In article < [email protected] ...>, >> The mpl developers are getting very close to the long-awaited v1.1.0 >> release >> of matplotlib. Before we do so, we are doing some final checking of the >> documentation to make sure that all critical pieces of information iss >> correct and up to date. >> >> In checking over the instructions for building and installing matplotlib >> on >> MacOSX, I have found two separate sets of instructions.

On the install >> page, there is a reference to a README.txt file in "release/osx". This >> file >> is there, but it seems to refer to other files that no longer exists. >> Meanwhile, there is an un-referenced file in the top directory called >> README.osx that seems a lot more current. >> >> Because I do not have a Mac that I can use for development, I would like >> to >> ask the community for help in determining the correct set of instructions >> and to eliminate cruft.

I think it would also be useful to point users to >> any relevant instructions for installing/building numpy on Macs. I would >> also like to make sure we are current with information on installing on a >> stock Lion install. >> >> Please feel free to respond on this list, or better, make a branch on >> github >> and submit pull requests to help us improve these documents. > > I wrote both of those files originally (make.osx and releases/osx/*). > The original division of labor was the stuff in "releases" was > designed to build the release binaries, and the stuff in make.osx was > primarily used to build from svn or src.

Overtime, most of the effort > has gone into make.osx, and it now includes support for binaries. I > no longer build the OSX binaries (Russell does) and no longer use OS X > (back to ubuntu) so if Russell is not using the stuff in releases/osx, > we can flush it. The releases/win32/ tree is also unmaintained since 0.99.0.rc1. Who does the Windows builds these days? Christophe? It would be nice to have a maintained record of how release builds are done, or better yet, up-to-date scripts that fully automate it.

Just for the record, I follow my own instructions to build the Mac binaries < http://www.astro.washington.edu/users/rowen/BuildingMatplotlibForMac.htm . I already have the libraries built and ready to go (I boot off a special drive configured for this task). Most of the remaining work involves working around bugs/misfeatures such as needing to edit setupext.py and checking for permission errors (thankfully not seen in 1.0.1), and I'm not sure how easy that would be to script.

I look forward to the day that the Mac binaries can be built using Apple's own libraries, but I think that's not likely to happen until python.org stops supporting PPC machines. -- Russell ··· Eric Firing < [email protected] ...> wrote: On 08/16/2011 10:10 AM, John Hunter wrote: > On Mon, Aug 15, 2011 at 9:34 PM, Benjamin > > Root< [email protected] ...> wrote: Andy_Somogyi August 17, 2011, 8:42pm 2 Why do you need to download and build png, zlib, freetype?

I build matplotlib semi-regularly on 10.6.8 using the built in libraries and it works perfectly fine. I built with both gcc 4.2 / 4.6 and llvm and all work fine. I use official Python 2.7.2 from python.org. Note, I have never tried building a universal binary, PPC is dead. On a side note, I'm getting ready to move my stuff (mostly C) to Python 3.2, does matploblib build with Py3K? ··· On Aug 17, 2011, at 2:45 PM, Russell E.

Owen wrote: In article < [email protected] ...>, Eric Firing < [email protected] ...> wrote: On 08/16/2011 10:10 AM, John Hunter wrote: On Mon, Aug 15, 2011 at 9:34 PM, Benjamin >>> Root< [email protected] ...> wrote: The mpl developers are getting very close to the long-awaited v1.1.0 release of matplotlib. Before we do so, we are doing some final checking of the documentation to make sure that all critical pieces of information iss correct and up to date.

In checking over the instructions for building and installing matplotlib on MacOSX, I have found two separate sets of instructions. On the install page, there is a reference to a README.txt file in "release/osx". This file is there, but it seems to refer to other files that no longer exists. Meanwhile, there is an un-referenced file in the top directory called README.osx that seems a lot more current. Because I do not have a Mac that I can use for development, I would like to ask the community for help in determining the correct set of instructions and to eliminate cruft.

I think it would also be useful to point users to any relevant instructions for installing/building numpy on Macs. I would also like to make sure we are current with information on installing on a stock Lion install. Please feel free to respond on this list, or better, make a branch on github and submit pull requests to help us improve these documents. I wrote both of those files originally (make.osx and releases/osx/*).

The original division of labor was the stuff in "releases" was designed to build the release binaries, and the stuff in make.osx was primarily used to build from svn or src. Overtime, most of the effort has gone into make.osx, and it now includes support for binaries. I no longer build the OSX binaries (Russell does) and no longer use OS X (back to ubuntu) so if Russell is not using the stuff in releases/osx, we can flush it.

The releases/win32/ tree is also unmaintained since 0.99.0.rc1. Who does the Windows builds these days? Christophe? It would be nice to have a maintained record of how release builds are done, or better yet, up-to-date scripts that fully automate it. Just for the record, I follow my own instructions to build the Mac binaries < http://www.astro.washington.edu/users/rowen/BuildingMatplotlibForMac.htm >. I already have the libraries built and ready to go (I boot off a special drive configured for this task).

Most of the remaining work involves working around bugs/misfeatures such as needing to edit setupext.py and checking for permission errors (thankfully not seen in 1.0.1), and I'm not sure how easy that would be to script. I look forward to the day that the Mac binaries can be built using Apple's own libraries, but I think that's not likely to happen until python.org stops supporting PPC machines. -- Russell ------------------------------------------------------------------------------ Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration.

Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 _______________________________________________ Matplotlib-devel mailing list [email protected] matplotlib-devel List Signup and Options Eric_Firing2 August 17, 2011, 9:07pm 3 Why do you need to download and build png, zlib, freetype? I build matplotlib semi-regularly on 10.6.8 using the built in libraries and it works perfectly fine.

I built with both gcc 4.2 / 4.6 and llvm and all work fine. I use official Python 2.7.2 from python.org. Note, I have never tried building a universal binary, PPC is dead. Thanks for the report. On a side note, I'm getting ready to move my stuff (mostly C) to Python 3.2, does matploblib build with Py3K? There is a separate repo for 3.x. The big job after the release of 1.1.0 (within a week or two, I hope) will be merging that 3.x branch into master so that we will be following numpy in having a single master branch that works for 2.6, 2.7, and >= 3.1 (or maybe 3.2--I don't know).

Not all gui backends are available for 3.x, so there will still be limitations. Eric ··· On 08/17/2011 10:42 AM, Andy Somogyi wrote: On Aug 17, 2011, at 2:45 PM, Russell E. Owen wrote: In article< [email protected] ...>, Eric Firing< [email protected] ...> wrote: On 08/16/2011 10:10 AM, John Hunter wrote: On Mon, Aug 15, 2011 at 9:34 PM, Benjamin >>>> Root< [email protected] ...> wrot

The rest of this page is on the live site.