[Python-Dev] transitioning from % to {} formatting
Benjamin Peterson
benjamin at python.org
Mon Oct 5 04:07:52 CEST 2009
More information about the Python-Dev mailing list
Mon Oct 5 04:07:52 CEST 2009
- Previous message: [Python-Dev] transitioning from % to {} formatting
- Next message: [Python-Dev] eggs now mandatory for pypi?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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
- Previous message: [Python-Dev] transitioning from % to {} formatting
- Next message: [Python-Dev] eggs now mandatory for pypi?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list