[Python-ideas] Deprecating rarely used str methods

Chris Angelico rosuav at gmail.com
Sat Aug 10 05:58:41 CEST 2013


On Sat, Aug 10, 2013 at 3:42 AM, Andrew Barnert <abarnert at yahoo.com> wrote:
> On Aug 9, 2013, at 15:11, Chris Angelico <rosuav at gmail.com> wrote:
>
>> On Fri, Aug 9, 2013 at 9:25 PM,  <random832 at fastmail.us> wrote:
>>> I would add str % stuff to the list of things that should be
>>> deprecated... has anyone done any work on a converter for that, that
>>> could be included in a hypothetical 3to4?
>>
>> Why should it be deprecated, though?
>
> I agree that there's no point arguing this out yet again.
>
> But I don't understand why so many people seem so baffled by the opposite position. Having two very different and relatively complex mini languages for the same purpose is a burden. Not having the same format strings as every other language in the world would also be a burden. Nobody can seriously believe that the other side really doesn't understand their point when the points are this obvious.


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.

ChrisA


More information about the Python-ideas mailing list