RetroSearch Browse

Thu Oct 8 17:52:20 CEST 2009 · https://mail.python.org/pipermail/python-dev/2009-October/092791.html

Eric Smith wrote:
> Vinay Sajip wrote:
>> BTW I sent Eric a private mail re. the "0o" versus "0" issue, to see 
>> if it was
>> worth raising an enhancement request on the bug tracker using "O" to 
>> generate
>> compatible rendering for octals.
> 
> I didn't get your message, could you resend?.
> 
> I was thinking the same thing, but it seems like a transition step. I'd 
> rather not keep such backward compatibility hacks (if you will) around 
> for the long haul.  How about a flag (maybe '*') at the start of the 
> format specification which says "operate in backward compatibility 
> mode"? We could document it as being only useful for the % to {} 
> translator, and promise to remove it at some point in the future. Either 
> actually deprecate it or just promise to deprecate it in the future.
> 
I think the flag should be '%'.

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2009-October/092791.html below:

[Python-Dev] transitioning from % to {} formatting