matplotlib-devel Mailing List for matplotlib (Page 2)

I'm tinkering with your example a little bit, but clicking on the legend 
items doesn't seem to do anything whether it contains the offending 
clipPath snippet or not. What version of matplotlib are you using? 
What browser (and version) are you using to interact with the SVG? Can 
you attach the SVG file (maybe in both working and broken states), so I 
can tinker with it? You may want to try moving the "<defs>" containing 
the clipPath up a level, so it is a peer with the histogram rectangles. 
That's just a stab in the dark. If that turns out that makes the 
difference, that should be an easy enough fix within matplotlib.
Cheers,
Mike
On 08/22/2011 10:57 AM, David Huard wrote:
> Hi,
>
> I'm trying to create an SVG figure that will show or hide the bars of
> a histogram when clicking on the element in the legend. I got to the
> point where it almost works...
>
> I'm including the script so that others can play with it, but from
> what I understand, the problem is that the first histogram patch
> definition includes a clipping path definition
>
> <defs>
> <clipPath id="p7ff5b81e1d">
> <rect height="345.6" width="446.4" x="72.0" y="43.2" />
> </clipPath>
> </defs>
>
> that is referenced by all other histogram patches. When setting the
> visibility attribute of the first patch to "hidden" , it hides all
> patches.
>
> If I remove this clipping path entirely (by hand), the interactive
> components work as expected.
>
> This is my first foray in SVG so my approach is probably naive, but
> I'd welcome suggestions to make this work. Having one clippath per
> histogram item would simplify things, but I don't know the internals
> of matplotlib well enough to do this elegantly.
>
> Thanks,
>
> David
>
>
> ------------------------------------------------------------------------------
> uberSVN's rich system and user administration capabilities and model
> configuration take the hassle out of deploying and managing Subversion and
> the tools developers use with it. Learn more about uberSVN and get a free
> download at: http://p.sf.net/sfu/wandisco-dev2dev
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Hi,
I'm trying to create an SVG figure that will show or hide the bars of
a histogram when clicking on the element in the legend. I got to the
point where it almost works...
I'm including the script so that others can play with it, but from
what I understand, the problem is that the first histogram patch
definition includes a clipping path definition
 <defs>
 <clipPath id="p7ff5b81e1d">
 <rect height="345.6" width="446.4" x="72.0" y="43.2" />
 </clipPath>
 </defs>
 that is referenced by all other histogram patches. When setting the
visibility attribute of the first patch to "hidden" , it hides all
patches.
If I remove this clipping path entirely (by hand), the interactive
components work as expected.
This is my first foray in SVG so my approach is probably naive, but
I'd welcome suggestions to make this work. Having one clippath per
histogram item would simplify things, but I don't know the internals
of matplotlib well enough to do this elegantly.
Thanks,
David

On 22/08/2011, at 5:36, Benjamin Root wrote:
> Ok, there has been a lot of useful discussion (for both MacOSX and Windows), but in the end, I want to know this: Is it possible for matplotlib to provide a single, recommended, fully-supported-by-us method for installing our package (possibly for each platform?). Could it be pip? Or some other option?
> 
> It is kinda sad that the linux install instructions are easier than the other platform instructions, and I don't think we even provide a linux installer.
It's pretty easy using MacPorts (thank you MacPorts maintainers :)
sudo port install py27-matplotlib
Obviously that doesn't help when building a dev version, although you can build out of tree ports.
--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
 -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C

On 08/21/2011 10:06 AM, Benjamin Root wrote:
> Ok, there has been a lot of useful discussion (for both MacOSX and
> Windows), but in the end, I want to know this: Is it possible for
> matplotlib to provide a single, recommended, fully-supported-by-us
> method for installing our package (possibly for each platform?). Could
> it be pip? Or some other option?
We do that via the installers built by Christoph for Windows and by 
Russell for OS X. Beyond that, for compiling from source, it is a 
matter of recipes that work for various platforms under various 
circumstances; there are just too many variables.
Perhaps the situation for OS X doesn't have to be quite as bad as it 
sometimes looks. make.osx works, or did the last time I tried it, but 
requires periodic maintenance. We could probably do what Russell 
recommends and restore darwin library locations to setupext.py, and then 
a plain setup-based build and install would work for many people. It 
might be worth trying, to see if it leads to more traffic on the list, 
or to less.
My sense is that pip and easy-install cause more trouble for mpl than 
they are worth.
>
> It is kinda sad that the linux install instructions are easier than the
> other platform instructions, and I don't think we even provide a linux
> installer.
Distros provide packages, so that's the equivalent of "installer" for 
linux; we provide git, tarballs, and notes as to what header files or 
devel packages need to be in place if one wants to compile from source.
Eric
>
> Ben Root

FYI
---------- Forwarded message ----------
From: Grahame Bowland <gr...@an...>
Date: Sun, Aug 21, 2011 at 2:18 AM
Subject: [IPython-dev] Announcing shrubbery
To: ipy...@sc...
Hi everyone
I've spent the last few days coming up with a Python 3 distribution of
iPython and friends for Mac OS X. It now works (mostly), and I thought
I'd share it.
The home page is here:
https://github.com/grahame/shrubbery
and I've put an experimental installer image here:
https://github.com/downloads/grahame/shrubbery/shrubbery.pkg
For a long time I've maintained my Python setup by hand, installing
packages into /usr/local and eventually having a huge mess. Hence this
project - a distribution of software for Mac OS to make it easier for
people to get started with iPython.
I've targeted Python 3 in the hope it'll encourage the porting of more
software to the new version of the language.
There's not too much Mac OS specific about this, except that on Linux
you'd probably want to get packages from your distribution. If anyone
wants to make it work on other platforms that'd be great.
Cheers
Grahame
_______________________________________________
IPython-dev mailing list
IPy...@sc...
http://mail.scipy.org/mailman/listinfo/ipython-dev

Ok, there has been a lot of useful discussion (for both MacOSX and Windows),
but in the end, I want to know this: Is it possible for matplotlib to
provide a single, recommended, fully-supported-by-us method for installing
our package (possibly for each platform?). Could it be pip? Or some other
option?
It is kinda sad that the linux install instructions are easier than the
other platform instructions, and I don't think we even provide a linux
installer.
Ben Root

Trailing whitespace has been creeping back into the sources; if you are 
committing to git, please check that you are not introducing it into the 
files you modify.
Eric

> From: Christoph Gohlke [mailto:cg...@uc...] 
> Sent: Wednesday, August 17, 2011 04:49
> 
> On 8/16/2011 11:12 PM, Eric Firing wrote:
> >
> > 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 started down that path, but I ended up using a simple CMD script instead of
a Makefile. It takes the approach you described below of preparing include
and link flags and then calling "python setup...". I've attached it as an
example for the mailing list, but note that the paths are specific to my
directory layout and to how I prepared the dependencies. I've also attached
my notes from building the dependencies. The versions described there are
circa November 2010.
> 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.

There were a couple of bug fixes in maint that had not yet been merged 
into master, so I just did that. I'm pretty sure it is OK, but in view 
of the impending release, checking and testing is particularly welcome.
Eric

Hi,
This is an extended version of the problems I reported yesterday to the user
listserv here:
http://sourceforge.net/mailarchive/message.php?msg_id=27953357
The basic problem is that key press events for the navigation keys ('up,
'down', 'left', 'right', 'pageup', and 'pagedown') are handled differently
for different backends. This leads to different behaviour when code is run
on a different backend.
Here are my observations:
Tk: -all navigation keys yield the correct event.key values.
 -nav keys are not bound to interactive toolbar
Qt4: -navigation keys all yield 'none'
 -nav keys are not bound to the interactive toolbar
GTK: -navigation keys yield the correct event.key values
 -the nav keys are bound to the interactive toolbar, but in an
inconsistant manner. If the toolbar zoom has not been used then up, left,
and right keys all send events to the connected key handler. If the toolbar
zoom has been used then left and right scrolls through the zoom levels.
Pressing the 'down' key selects the interactive toolbar, further presses of
any key are no longer sent to the connected key_press_event callbacks, but
they do change the selected tool. The zoom behaviour of the left and right
keys can be removed by unconnecting the toolbar's key_press_event handler.
But, this does not change that of the down key: whatever selects the toolbar
upon pressing the 'down' key is at a lower level than matplotlib.
This seems like bad behaviour. My impression has been that code should work
equally well with all backends.
For my application, my preferred backend is GTK, but my desired behaviour is
that of Ag. Can anyone recommend how to get GTK to not select the toolbar
with the down key (while keeping the toolbar)?
Thanks for your help,
-AM

On Wed, Aug 17, 2011 at 7:33 PM, Christoph Gohlke <cg...@uc...> wrote:
> 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.
>
Right. Thanks. I got some ways there building zlib dependency with
nmake and/or vcbuild. They appear to be working at least.
> >
> > 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.
>
Thanks, that did the trick. Working mpl from source on windows 7,
python 2.7, 64-bit.
Skipper
> 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
>
> ------------------------------------------------------------------------------
> 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

Hello,
I want to plot a scalar function on the sphere in a Mollweide 
projection. My strategy is to:
 1. Generate a rectangular mesh in display coordinates,
 2. Apply the inverse transform for the Mollweide projection to get 
the data coordinates of every display coordinate,
 3. Evaluate the function at each data coordinate, and finally,
 4. Plot with imshow.
I noticed that the inverse transform in 
matplotlib.projections.geo.MollweideAxes is not implemented. I'm 
attaching a patch that fills in the missing inverse.
Also attached is a minimal example of the type of plot I am interested 
in making.
Cheers,
Leo Singer
Graduate Student @ LIGO-Caltech

On 08/17/2011 09:34 PM, Jae-Joon Lee wrote:
> Hi Eric,
>
> I just pushed a commit that I believe fix the problem.
>
> https://github.com/matplotlib/matplotlib/commit/fcebc2338ad730098520c866122061eefd866641
>
> The documentation now builds fine in my linux box.
Excellent, thank you.
Eric
>
> Regards,
>
> -JJ
>
>
> On Tue, Aug 16, 2011 at 8:52 AM, Eric Firing<ef...@ha...> wrote:
>> On 08/15/2011 12:07 PM, Eric Firing wrote:
>>> JJ,
>>>
>>> Thanks for your fast fix of the last problem I reported.
>>>
>>> Now that the doc build is trying to run scripts with the __main__
>>> conditional, one of the examples it is tripping over is
>>> make_room_for_ylabel_using_axesgrid.py.
>>>
>>> When I try to run it on the command line or in ipython, it displays
>>> nothing at all. I suspect that is related to the failure in the doc
>>> build, but I haven't looked into it at all. (In the doc build it
>>> generates a huge traceback ending in
>>> RuntimeError: maximum recursion depth exceeded in __instancecheck__
>>> ).
>>
>> Correction: running it from the command line generates the same problem
>> as is seen in the doc build and described above.
>>
>> Eric
>>
>> ------------------------------------------------------------------------------
>> uberSVN's rich system and user administration capabilities and model
>> configuration take the hassle out of deploying and managing Subversion and
>> the tools developers use with it. Learn more about uberSVN and get a free
>> download at: http://p.sf.net/sfu/wandisco-dev2dev
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>

Hi Eric,
I just pushed a commit that I believe fix the problem.
https://github.com/matplotlib/matplotlib/commit/fcebc2338ad730098520c866122061eefd866641
The documentation now builds fine in my linux box.
Regards,
-JJ
On Tue, Aug 16, 2011 at 8:52 AM, Eric Firing <ef...@ha...> wrote:
> On 08/15/2011 12:07 PM, Eric Firing wrote:
>> JJ,
>>
>> Thanks for your fast fix of the last problem I reported.
>>
>> Now that the doc build is trying to run scripts with the __main__
>> conditional, one of the examples it is tripping over is
>> make_room_for_ylabel_using_axesgrid.py.
>>
>> When I try to run it on the command line or in ipython, it displays
>> nothing at all. I suspect that is related to the failure in the doc
>> build, but I haven't looked into it at all. (In the doc build it
>> generates a huge traceback ending in
>> RuntimeError: maximum recursion depth exceeded in __instancecheck__
>> ).
>
> Correction: running it from the command line generates the same problem
> as is seen in the doc build and described above.
>
> Eric
>
> ------------------------------------------------------------------------------
> uberSVN's rich system and user administration capabilities and model
> configuration take the hassle out of deploying and managing Subversion and
> the tools developers use with it. Learn more about uberSVN and get a free
> download at: http://p.sf.net/sfu/wandisco-dev2dev
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

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
>