[SciPy-dev] Plea for help

Christopher Hanley chanley@stsci....
Thu Aug 20 08:50:22 CDT 2009


Hi,

I'd like to respectfully request that we move any discussion of what  
to do with the numpy.char module to the numpy list.

I'm a little concerned about some of the assumptions that are being  
made about the number of users of the module.  I would also like to  
better understand the reasons for wanting to dump it.  Let me be  
clear.  I'm not opposed to change.  However breaking other people's  
code just for the sake of change seems like a poor reason and a mean  
thing to do to our customers.

Thank you for your time and help,
Chris


-- 
Christopher Hanley
Senior Systems Software Engineer
Space Telescope Science Institute
3700 San Martin Drive
Baltimore MD, 21218
(410) 338-4338

On Aug 20, 2009, at 1:35 AM, Robert Kern wrote:

> On Wed, Aug 19, 2009 at 20:03, David  
> Goldsmith<d_l_goldsmith@yahoo.com> wrote:
>> I'm going to take it a step further: "breakage" is always the  
>> deterrent to change, and yet "change we must" (i.e., "adapt or  
>> die").  It's certainly not without precedent - even within Numpy, I  
>> believe - for things (though perhaps not whole namespaces) to be  
>> deemed "to-be-deprecated," have a warning to this effect  
>> established in one x.[even #].0 release, and then be removed by the  
>> x.[even # + 2 or + 4].0 release.  How has deprecation in Numpy  
>> worked in the past - by dictum, vote, or consensus?
>
> Consensus or dictum without major objection. Voting is pointless
> except to inform one of those.
>
> -- 
> 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
> _______________________________________________
> Scipy-dev mailing list
> Scipy-dev@scipy.org
> http://mail.scipy.org/mailman/listinfo/scipy-dev



More information about the Scipy-dev mailing list