On Fri, Jun 20, 2008 at 15:17, Sebastian Haase <[EMAIL PROTECTED]> wrote: > On Fri, Jun 20, 2008 at 9:37 AM, David Cournapeau > <[EMAIL PROTECTED]> wrote: >> Robert Kern wrote: >>> >>> They should deprecated for one minor version and then deleted. >> >> Ok, thanks for the clarification. Since I was not aware of this, and did >> not see this information on the wiki, I added it in >> http://scipy.org/scipy/numpy/wiki/ApiDeprecation. Let me know if there >> is something I misunderstood from your remarks, >> > Hi David, > you say: > """For example, if a function is deprecated in numpy 1.1.0, it will > remain so in all 1.1.x releases, but it can and should be removed in > 1.2.0. """ > > But what if, say, with version 1.1.2 we decide to change a given > default argument. So you get the deprecation warning starting with > 1.1.2. > But now, if this happens to be the last version of 1.1.x. -- you say > that already with the next version ( being 1.2.0 ) it would change > without a deprecation warning given anymore !?
You missed this part (emphasis added): "Deprecation warnings should exist for *one*full*minor*release*cycle* before the deprecated features are removed." -- 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 _______________________________________________ Numpy-discussion mailing list [email protected] http://projects.scipy.org/mailman/listinfo/numpy-discussion
