Re: [boost] [gil] Ok to merge new gil's extension to release branch?

Subject: Re: [boost] [gil] Ok to merge new gil's extension to release branch?
From: Christian Henning (chhenning_at_[hidden])
Date: 2013-04-16 21:14:14

On Mon, Apr 15, 2013 at 9:33 PM, Steven Watanabe <watanabesj_at_[hidden]>wrote:

> AMDG
>
> On 04/15/2013 05:45 PM, Christian Henning wrote:
> > Sorry I thought it failed due to:
> >
> > Failed to match input file contents: $test.cpp
> > etc.
> >
> > I think this one failed:
> >
> > http://pastebin.com/kgQkBxKz
> >
>
> Aha.  I think I know what the problem is.
> The .pyc file isn't getting updated after
> the new .py file is written.  The resolution
> must be too low on the timestamps that
> Python is using.  See if my last commit fixes this.
>
>
I think it looks good now!

stdout seems to be consisted to:

http://pastebin.com/BtKReYJR

Looks like we got out the kinks. The next step is to create tests for the
remaining 3rd party libs.

Thank you very much!

Christian