2009/10/4 INADA Naoki <songofacandy at gmail.com>:
>> -1 That requires keeping formatting information around in every string instance.
> Adding new "format_string" class avoids it.
> unicode("foo") <=> u"foo"
> format_string("foo") <=> f"foo"
>
> This way's pros:
> * Many libraries can use one transition way.
> * Transition stage syncs to Python version. "library A uses {} and
> library B uses %" problem not happen in transition.
> * We have experience same way on unicode.
And all are outweighted by the introduction of a new string class.
--
Regards,
Benjamin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4