Re: [matplotlib-devel] Binary release process

[Darren D. <dsd...@gm...>]

On Sun, Dec 14, 2008 at 1:58 PM, Charlie Moad <cw...@gm...> wrote:

> On Sun, Dec 14, 2008 at 1:22 PM, Darren Dale <dsd...@gm...> wrote:
> > On Sun, Dec 14, 2008 at 12:24 PM, Charlie Moad <cw...@gm...> wrote:
> >>
> >>     First of all let me apologize for the problems we have been
> >> seeing with the binaries as of late.  Frankly the root of the problem
> >> might be my detachment from the matplotlib source for some time.
> >> Unfortunately due to my time constraints, this won't be changing soon.
> >>  I used to think being somewhat on the outside helped me keep the ease
> >> of the build process in check.  This gap has apparently grown too
> >> wide.
> >
> > I appreciate that this is a difficult task and that you have plenty of
> other
> > responsibilities, and appreciate your effort. However, I've been trying
> to
> > get to the bottom of why the windows installer is overwriting configobj
> and
> > I could use some feedback from you. I really need to know whether you
> delete
> > the build/ directory before creating a new installer.
>
> I don't have my build directories anymore, but they were made from
> extracting the source release so there was no previous build
> directory.  It is possible that I missed those settings in setup.cfg,
> because I do not have either of those module installed.
>

If you did not explicitly disable these modules in setup.cfg, then I think
we understand the problem. Would you please make a note that configobj and
traits should be explicitly disabled in setup.cfg for future releases of the
maintenance branches? It will not be an issue for the trunk.

Thanks,
Darren