[Python-ideas] Deprecating rarely used str methods

[Chris Angelico]

On Sat, Aug 10, 2013 at 6:36 AM, Joshua Landau <joshua at landau.ws> wrote:
> On 10 August 2013 04:58, Chris Angelico <rosuav at gmail.com> wrote:
>> Oh, I can see the other side's arguments. If str.format existed and
>> str% didn't, there would be insufficient grounds to add it. But they
>> both exist, and the arguments for removing a feature have to be
>> insanely strong. Status quo wins easily.
>
> But the arguments for deprecating a feature in favour of the other (so
> as to aid standardisation) without imminent removal plans don't have
> to be as strong.

What does deprecation mean if you aren't planning to remove it? Why
should I change my code if it's not going to break? Deprecation has to
be backed by intent to remove.

ChrisA