Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

[Michael D. <md...@st...>]

On 07/31/2013 05:12 PM, Russell E. Owen wrote:
> In article <51F...@st...>,
>   Michael Droettboom <md...@st...>
>   wrote:
>
>> On 07/31/2013 01:47 PM, Russell E. Owen wrote:
>>> In article <51F...@st...>,
>>>    Michael Droettboom <md...@st...>
>>>    wrote:
>>>
>>>> I have tagged and uploaded matplotlib 1.3.0 final.  Congratulations to
>>>> all involved!  It was a long slog getting this release out, and I
>>>> appreciate everyone's patience.
>>>>
>>>> Once we have binaries uploaded to SourceForge, I will make a formal
>>>> announcement in the usual channels.
>>> I built the Mac binary on MacOS X 10.6 but have run into two problems:
>>> - Most of the unit tests are missing, so I can't properly test the
>>> results. But my application that uses matplotlib and TkAgg works fine,
>>> so may well be OK. Also, I checked and the installer was trying to build
>>> all expected backends (including the native Mac backend).
>> What do you mean the unit tests are missing?  They don't run?  Can you
>> send the output from nose?
>>
>> Glad to hear about the installer building the macosx backend -- that was
>> pretty serious when it wasn't doing that.
> Yes.
>
> All the interesting information about a build is printed at the
> beginning and soon scrolls out of sight, so it's usually not obvious if
> a build is missing something expected.
>
> That seems to be standard for unix and distutils installers, so I
> suspect it would not be trivial to change. Would it make sense to add a
> unit test that verifies the mac backend was built?
>
That's a good idea.  And we skip it on other platforms ;)

Mike