> In article
> ,
> 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 (possibl
In article
,
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
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 fo
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
op
> From: Christoph Gohlke [mailto:cgoh...@uci.edu]
> 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 ha
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 wrote:
>>
>>> The only thing worth providing might be the prebuilt static link libraries
>>> and header files for zlib, libpng, and freetype fo
On Wed, Aug 17, 2011 at 3:42 PM, 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
> officia
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
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 build
On 8/17/2011 12:03 PM, Skipper Seabold wrote:
> On Wed, Aug 17, 2011 at 4:49 AM, Christoph Gohlke wrote:
>
>> 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.
>
>
On Wed, Aug 17, 2011 at 4:49 AM, Christoph Gohlke wrote:
> 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
In article <4e4b5be2.8040...@hawaii.edu>,
Eric Firing wrote:
> On 08/16/2011 10:10 AM, John Hunter wrote:
> > On Mon, Aug 15, 2011 at 9:34 PM, Benjamin
> > Root wrote:
> >> The mpl developers are getting very close to the long-awaited v1.1.0
> >> release
> >> of matplotlib. Before we do so,
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 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
On 08/16/2011 10:10 AM, John Hunter wrote:
> On Mon, Aug 15, 2011 at 9:34 PM, Benjamin Root 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 crit
On Mon, Aug 15, 2011 at 9:34 PM, Benjamin Root 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
In article
,
Benjamin Root 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
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 in
17 matches
Mail list logo