(original) (raw)

On 01/28/2014 04:37 AM, Steven D'Aprano wrote:

On Mon, Jan 27, 2014 at 10:06:57PM -0800, Larry Hastings wrote:

.. note: if "times" is specified using a keyword argument, and
provided with a negative value, repeat yields the object forever.
This is a bug, its use is unsupported, and this behavior may be
removed in a future version of Python.

How about changing "may be removed" to "will be removed", he asks
hopefully? :-)

+1

\* A good use for deprecations is for features that were flat-out misdesigned

and prone to error. For those, there is nothing wrong with deprecating them

right away. Once deprecated though, there doesn't need to be a rush to

actually remove it -- that just makes it harder for people with currently

working code to upgrade to newer versions of Python.

\* When I became a core developer well over a decade ago, I was a little

deprecation happy (old stuff must go, keep everything nice and clean, etc).

What I learned though is that deprecations are very hard on users and that

the purported benefits usually aren't really important.