Re: [matplotlib-devel] requesting permission to remove traits and configobj

On Wed, Dec 10, 2008 at 11:10 PM, John Hunter <jd...@gm...> wrote:

>
>
> On Wed, Dec 10, 2008 at 9:20 PM, Darren Dale <dsd...@gm...> wrote:
>
>> There has been a report at the bugtracker complaining that matplotlib is
>> overwriting an existing installation of configobj. I had a look at the code
>> and thought the bug report must be a mistake or windows specific, but I just
>> saw similar behavior on my linux system.
>
>
> Ignoring for a minute the question of whether we can/should flush
> configobj/traits, it sounds like the real problem is that setup.cfg is not
> working like we expect it to.  And that is something that should be fixed if
> is broken.  If mpl is installing configobj or traits even if we are telling
> it not to via setup.cfg, then we have a problem.   This is worth knowing,
> since the last mpl release was broken vis-a-vis the default backend on
> win32, which *could* be explained by a broken setup.cfg.
>
>
> I would like to simply remove configobj and traits from our repository.
>> They are only used by the long-neglected experimental traited config
>> package, which is only of interest to developers who can easily install them
>> as external dependencies. Is it ok to remove them? If so, should it be done
>> on all the branches?
>>
> [...]

>
> You can remove them from the trunk.  They should remain on the 0.91 branch
> as is (with any known bugs fixed and merged) since that is the point of the
> branch (stability for those who cannot upgrade -- in principle someone might
> be depending on the traited config, in practice unlikely).
>

I just removed them from the trunk, but not the 0.91 or 0.98.5 branches. I
was going to add a note to the API_CHANGES log, was it removed?