[SciPy-Dev] deprecations - things to remove before 0.8.0
Robert Kern
robert.kern at gmail.com
Thu May 27 21:00:32 EDT 2010
On Thu, May 27, 2010 at 20:58, Warren Weckesser
<warren.weckesser at enthought.com> wrote:
> David wrote:
>> It does not to me. Keeping python code has *no* cost from a maintainance
>> point of view (contrary to compiled code which may be a pain to allow it
>> to build),
>
> Since you specifically emphasized "no", I will respectfully disagree
> with you about that. I spent time fixing a bug in ppimport, before I
> knew that it was deprecated and no longer had a use in scipy--and that
> it had additional problems besides the small ones I fixed. My questions
> about ppimport took up time of other developers. Developers' time is a
> cost. Code that is not going to be maintained, or that no longer solves
> a problem within the scope of SciPy, should be removed.
>
> But not until is has been deprecated for at least one release. :)
"Keeping [properly-marked-deprecated] python code has *no* cost from a
maintenance point of view ...."
--
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless
enigma that is made terrible by our own mad attempt to interpret it as
though it had an underlying truth."
-- Umberto Eco
More information about the SciPy-Dev
mailing list