matplotlib-devel Mailing List for matplotlib

On 8/17/2011 4:05 PM, Skipper Seabold wrote:
> On Wed, Aug 17, 2011 at 4:21 PM, Christoph Gohlke <cg...@uc...
> <mailto:cg...@uc...>> wrote:
>>
>>
>> On 8/17/2011 12:03 PM, Skipper Seabold wrote:
>> > On Wed, Aug 17, 2011 at 4:49 AM, Christoph Gohlke<cg...@uc...
> <mailto:cg...@uc...>> wrote:
>> > <snip>
>> >> The only thing worth providing might be the prebuilt static link
> libraries
>> >> and header files for zlib, libpng, and freetype for the 4 different MSC
>> >> compilers/runtime libraries.
>> >
>> > This would be very helpful. I haven't been able to track down the
>> > plot_directive bugs on windows, because I haven't been able to build
>> > the dependencies with any luck.
>> >
>> > Skipper
>> >
>>
>>
>> OK. I uploaded matplotlib-1.x-windows-link-libraries.zip at
>> <http://www.lfd.uci.edu/~gohlke/pythonlibs/#matplotlib>.
>>
>
> That's awesome. Thanks!
>
>> The archive contains zlib-1.2.5, libpng-1.4.8, and freetype-2.4.6 link
>> libraries and header files for the build systems listed below.
>>
>> All other Python package dependencies can also be downloaded from that
>> page. Let me know if anything is missing.
>>
>> A description on how to build Python 2.6+ extensions using the free
>> Windows SDK 7.0 is at
>> <http://wiki.cython.org/64BitCythonExtensionsOnWindows>. I have not
>> tested it with mpl though.
>>
>
> This is how I've been building python packages with extension on Windows
> if I need to, but I wouldn't know how to build the dependencies. Can you
> recommend a good resource for doing so/learning to do so with SDK?
Almost every library is different. Some require CMake, others scons, 
devenv, nmake, Perl... Refer to the readme or install files.
>
> Now for MPL, I just dropped the msvcr90-x64 files into my matplotlib
> source directory because I got tired of messing with setupext.py to try
> to point to them.
Try adding the directory containing the lib and include files to the LIB 
and INCLUDE environment variables.
>I receive the following error
>
> <snip>
> c:\users\skipper\src\matplotlib\zconf.h(380) : fatal error C1083: Cannot
> open include file: 'unistd.h': No such file or directory
> error: Command "cl.exe /c /nologo /Ox /MD /W3 /GS- /DNDEBUG
> -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -I.
> -IC:\Python27\lib\site-packages\numpy\core\include -I.
> -IC:\Python27\include -IC:\Python27\PC /Tpsrc/_png.cpp
> /Fobuild\temp.win-amd64-2.7\Release\src/_png.obj" failed with exit status 2
>
> Whole build log is here: http://pastebin.com/EfxYjMnL
Use an empty unistd.h file. I have added that to the zip file.
Christoph
>
> Thanks,
>
> Skipper
>
>> Christoph
>>
>>
>> msvcr71-x32
>> -----------
>> Python 2.5 32 bit
>> Visual Studio .NET 2003
>> MS C Compiler 13.10
>> MSVCR71.DLL C runtime
>>
>> msvcrt-x64
>> ----------
>> Python 2.5 64 bit
>> Microsoft Platform SDK for Windows Server 2003 R2
>> MS C Compiler 13.10
>> MSVCRT.DLL C runtime
>>
>> msvcr90-x32
>> -----------
>> Python 2.6, 2.7, 3.1, 3.2 32 bit
>> Microsoft Visual Studio 2008 Pro
>> (or Microsoft Windows SDK v7.0 for Windows 7 and .NET Framework 3.5
>> Service Pack 1)
>> MS C Compiler 15.0
>> MSVCR90.DLL C runtime
>>
>> msvcr90-x64
>> -----------
>> Python 2.6, 2.7, 3.1, 3.2 64 bit
>> Microsoft Visual Studio 2008 Pro
>> (or Microsoft Windows SDK v7.0 for Windows 7 and .NET Framework 3.5
>> Service Pack 1)
>> MS C Compiler 15.0
>> MSVCR90.DLL C runtime
>>
>
>
>
>
> ------------------------------------------------------------------------------
> 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
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

On Wed, Aug 17, 2011 at 4:21 PM, Christoph Gohlke <cg...@uc...> wrote:
>
>
> On 8/17/2011 12:03 PM, Skipper Seabold wrote:
>> On Wed, Aug 17, 2011 at 4:49 AM, Christoph Gohlke<cg...@uc...>
 wrote:
>> <snip>
>>> The only thing worth providing might be the prebuilt static link
libraries
>>> and header files for zlib, libpng, and freetype for the 4 different MSC
>>> compilers/runtime libraries.
>>
>> This would be very helpful. I haven't been able to track down the
>> plot_directive bugs on windows, because I haven't been able to build
>> the dependencies with any luck.
>>
>> Skipper
>>
>
>
> OK. I uploaded matplotlib-1.x-windows-link-libraries.zip at
> <http://www.lfd.uci.edu/~gohlke/pythonlibs/#matplotlib>.
>
That's awesome. Thanks!
> The archive contains zlib-1.2.5, libpng-1.4.8, and freetype-2.4.6 link
> libraries and header files for the build systems listed below.
>
> All other Python package dependencies can also be downloaded from that
> page. Let me know if anything is missing.
>
> A description on how to build Python 2.6+ extensions using the free
> Windows SDK 7.0 is at
> <http://wiki.cython.org/64BitCythonExtensionsOnWindows>. I have not
> tested it with mpl though.
>
This is how I've been building python packages with extension on Windows if
I need to, but I wouldn't know how to build the dependencies. Can you
recommend a good resource for doing so/learning to do so with SDK?
Now for MPL, I just dropped the msvcr90-x64 files into my matplotlib source
directory because I got tired of messing with setupext.py to try to point to
them. I receive the following error
<snip>
c:\users\skipper\src\matplotlib\zconf.h(380) : fatal error C1083: Cannot
open include file: 'unistd.h': No such file or directory
error: Command "cl.exe /c /nologo /Ox /MD /W3 /GS- /DNDEBUG
-DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -I.
-IC:\Python27\lib\site-packages\numpy\core\include -I. -IC:\Python27\include
-IC:\Python27\PC /Tpsrc/_png.cpp
/Fobuild\temp.win-amd64-2.7\Release\src/_png.obj" failed with exit status 2
Whole build log is here: http://pastebin.com/EfxYjMnL
Thanks,
Skipper
> Christoph
>
>
> msvcr71-x32
> -----------
> Python 2.5 32 bit
> Visual Studio .NET 2003
> MS C Compiler 13.10
> MSVCR71.DLL C runtime
>
> msvcrt-x64
> ----------
> Python 2.5 64 bit
> Microsoft Platform SDK for Windows Server 2003 R2
> MS C Compiler 13.10
> MSVCRT.DLL C runtime
>
> msvcr90-x32
> -----------
> Python 2.6, 2.7, 3.1, 3.2 32 bit
> Microsoft Visual Studio 2008 Pro
> (or Microsoft Windows SDK v7.0 for Windows 7 and .NET Framework 3.5
> Service Pack 1)
> MS C Compiler 15.0
> MSVCR90.DLL C runtime
>
> msvcr90-x64
> -----------
> Python 2.6, 2.7, 3.1, 3.2 64 bit
> Microsoft Visual Studio 2008 Pro
> (or Microsoft Windows SDK v7.0 for Windows 7 and .NET Framework 3.5
> Service Pack 1)
> MS C Compiler 15.0
> MSVCR90.DLL C runtime
>

On 8/17/2011 1:21 PM, Christoph Gohlke wrote:
>
>
> On 8/17/2011 12:03 PM, Skipper Seabold wrote:
>> On Wed, Aug 17, 2011 at 4:49 AM, Christoph Gohlke<cg...@uc...> wrote:
>> <snip>
>>> The only thing worth providing might be the prebuilt static link libraries
>>> and header files for zlib, libpng, and freetype for the 4 different MSC
>>> compilers/runtime libraries.
>>
>> This would be very helpful. I haven't been able to track down the
>> plot_directive bugs on windows, because I haven't been able to build
>> the dependencies with any luck.
>>
>> Skipper
>>
>
>
> OK. I uploaded matplotlib-1.x-windows-link-libraries.zip at
> <http://www.lfd.uci.edu/~gohlke/pythonlibs/#matplotlib>.
>
> The archive contains zlib-1.2.5, libpng-1.4.8, and freetype-2.4.6 link
> libraries and header files for the build systems listed below.
>
> All other Python package dependencies can also be downloaded from that
> page. Let me know if anything is missing.
>
> A description on how to build Python 2.6+ extensions using the free
> Windows SDK 7.0 is at
> <http://wiki.cython.org/64BitCythonExtensionsOnWindows>. I have not
> tested it with mpl though.
>
> Christoph
>
>
> msvcr71-x32
> -----------
> Python 2.5 32 bit
> Visual Studio .NET 2003
> MS C Compiler 13.10
> MSVCR71.DLL C runtime
>
> msvcrt-x64
> ----------
> Python 2.5 64 bit
> Microsoft Platform SDK for Windows Server 2003 R2
> MS C Compiler 13.10
Correction: this should be version 14.00
Christoph
> MSVCRT.DLL C runtime
>
> msvcr90-x32
> -----------
> Python 2.6, 2.7, 3.1, 3.2 32 bit
> Microsoft Visual Studio 2008 Pro
> (or Microsoft Windows SDK v7.0 for Windows 7 and .NET Framework 3.5
> Service Pack 1)
> MS C Compiler 15.0
> MSVCR90.DLL C runtime
>
> msvcr90-x64
> -----------
> Python 2.6, 2.7, 3.1, 3.2 64 bit
> Microsoft Visual Studio 2008 Pro
> (or Microsoft Windows SDK v7.0 for Windows 7 and .NET Framework 3.5
> Service Pack 1)
> MS C Compiler 15.0
> MSVCR90.DLL C runtime
>
> ------------------------------------------------------------------------------
> 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
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>

On Wed, Aug 17, 2011 at 3:42 PM, Andy Somogyi <som...@um...> wrote:
> 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.
We do this for the binaries we distribute on windows and OSX because
we find there is so much variation in the wild (eg on OSX where did
libpng come from, what version) that it is safer and more robust to
link these in statically.
JDH

On 08/17/2011 10:42 AM, Andy Somogyi wrote:
> 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 Aug 17, 2011, at 2:45 PM, Russell E. Owen wrote:
>
>> In article<4E4...@ha...>,
>> Eric Firing<ef...@ha...> wrote:
>>
>>> On 08/16/2011 10:10 AM, John Hunter wrote:
>>>> On Mon, Aug 15, 2011 at 9:34 PM, Benjamin
>>>> Root<ben...@ou...> 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
>> l>. 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
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
> ------------------------------------------------------------------------------
> 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
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

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 <4E4...@ha...>,
> Eric Firing <ef...@ha...> wrote:
> 
>> On 08/16/2011 10:10 AM, John Hunter wrote:
>>> On Mon, Aug 15, 2011 at 9:34 PM, Benjamin 
>>> Root<ben...@ou...> 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
> l>. 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
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

On 8/17/2011 12:03 PM, Skipper Seabold wrote:
> On Wed, Aug 17, 2011 at 4:49 AM, Christoph Gohlke<cg...@uc...> wrote:
> <snip>
>> The only thing worth providing might be the prebuilt static link libraries
>> and header files for zlib, libpng, and freetype for the 4 different MSC
>> compilers/runtime libraries.
>
> This would be very helpful. I haven't been able to track down the
> plot_directive bugs on windows, because I haven't been able to build
> the dependencies with any luck.
>
> Skipper
>
OK. I uploaded matplotlib-1.x-windows-link-libraries.zip at 
<http://www.lfd.uci.edu/~gohlke/pythonlibs/#matplotlib>.
The archive contains zlib-1.2.5, libpng-1.4.8, and freetype-2.4.6 link 
libraries and header files for the build systems listed below.
All other Python package dependencies can also be downloaded from that 
page. Let me know if anything is missing.
A description on how to build Python 2.6+ extensions using the free 
Windows SDK 7.0 is at 
<http://wiki.cython.org/64BitCythonExtensionsOnWindows>. I have not 
tested it with mpl though.
Christoph
msvcr71-x32
-----------
Python 2.5 32 bit
Visual Studio .NET 2003
MS C Compiler 13.10
MSVCR71.DLL C runtime
msvcrt-x64
----------
Python 2.5 64 bit
Microsoft Platform SDK for Windows Server 2003 R2
MS C Compiler 13.10
MSVCRT.DLL C runtime
msvcr90-x32
-----------
Python 2.6, 2.7, 3.1, 3.2 32 bit
Microsoft Visual Studio 2008 Pro
(or Microsoft Windows SDK v7.0 for Windows 7 and .NET Framework 3.5 
Service Pack 1)
MS C Compiler 15.0
MSVCR90.DLL C runtime
msvcr90-x64
-----------
Python 2.6, 2.7, 3.1, 3.2 64 bit
Microsoft Visual Studio 2008 Pro
(or Microsoft Windows SDK v7.0 for Windows 7 and .NET Framework 3.5 
Service Pack 1)
MS C Compiler 15.0
MSVCR90.DLL C runtime

On Wed, Aug 17, 2011 at 4:49 AM, Christoph Gohlke <cg...@uc...> wrote:
<snip>
> The only thing worth providing might be the prebuilt static link libraries
> and header files for zlib, libpng, and freetype for the 4 different MSC
> compilers/runtime libraries.
This would be very helpful. I haven't been able to track down the
plot_directive bugs on windows, because I haven't been able to build
the dependencies with any luck.
Skipper

In article <4E4...@ha...>,
 Eric Firing <ef...@ha...> wrote:
> On 08/16/2011 10:10 AM, John Hunter wrote:
> > On Mon, Aug 15, 2011 at 9:34 PM, Benjamin 
> > Root<ben...@ou...> 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
l>. 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

Thanks for finding these. I have fixes here:
https://github.com/matplotlib/matplotlib/pull/426
This does get me thinking that we still have a number of tests in 
backend_driver that should be ported to the test framework -- I 
generally only run the test framework, but clearly the coverage is not 
adequate.
Mike
On 08/17/2011 04:00 AM, Eric Firing wrote:
> Running backend_driver:
>
> Backend svg took 4.94 minutes to complete
> Failures: ['../pylab_examples/quadmesh_demo.py', '../api/logo2.py',
> '../api/watermark_text.py']
>
> All the other backends passed. It looks like there is a single svg
> problem being triggered by all three of these examples.
>
> Eric
>
> ------------------------------------------------------------------------------
> 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
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

On 8/16/2011 11:12 PM, Eric Firing wrote:
> On 08/16/2011 10:10 AM, John Hunter wrote:
>> On Mon, Aug 15, 2011 at 9:34 PM, Benjamin Root<ben...@ou...> 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.
IIRC Stan West has updated those build scripts to work with Visual 
Studio 2008 Express.
I use Visual Studio and Windows SDK compilers, whatever is the 
officially documented and supported compiler by the targeted Python 
version. I don't use anything from the mpl/releases/win32 tree but 
follow the instructions at 
<http://matplotlib.sourceforge.net/users/installing.html> and 
<http://docs.python.org/distutils/builtdist.html>: run `python setup.py 
bdist_wininst` after customizing setup.cfg and manually 
building/installing all required and optional dependencies, making sure 
they can be found by setup.py (e.g. via environment variables). I don't 
think it is reasonable or necessary to fully automate this process 
involving 10 python versions, ~10 dependencies, 4 compilers, and several 
helper programs (CMake, nasm, git, tar, zip, miktex, Ghostscript). The 
only thing worth providing might be the prebuilt static link libraries 
and header files for zlib, libpng, and freetype for the 4 different MSC 
compilers/runtime libraries.
Christoph
>
> Eric
>
>>
>> JDH
>

Running backend_driver:
Backend svg took 4.94 minutes to complete
 Failures: ['../pylab_examples/quadmesh_demo.py', '../api/logo2.py', 
'../api/watermark_text.py']
All the other backends passed. It looks like there is a single svg 
problem being triggered by all three of these examples.
Eric

On 08/16/2011 10:10 AM, John Hunter wrote:
> On Mon, Aug 15, 2011 at 9:34 PM, Benjamin Root<ben...@ou...> 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.
Eric
>
> JDH