py3k concerns. An example

[Hrvoje Niksic]

"Martin v. Löwis" <martin at v.loewis.de> writes:

>>>> In py3k string%dictionary is going away.
>>> Why do you say that? It's not going away in Python 3.0.
>> 
>> I also got the impression that it was going away.  PEP 3101's abstract
>> says:
>> 
>>     This PEP proposes a new system for built-in string formatting
>>     operations, intended as a replacement [sic] for the existing '%'
>>     string formatting operator.
>> 
>> Under "Backward compatibility" it says that both systems can coexist
>> "until it comes time to deprecate the older system".
>
> The PEP may say that it's going away, but it doesn't say that it
> goes away in 3.0 - and indeed, it won't.

Thanks for clarifying it.  It is certainly unclear from the wording of
the PEP, given that 3.0 is regarded as the Python version allowed to
break backward compatibility.

> At some point in the future, somebody will likely propose that the
> PEP will be executed. At that time, huge flame wars will start. I
> expect that they settle in changing the PEP to explain that the old
> mechanism gets removed in Python 4, to be release in 2018 :-)

Indeed.