This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author durin42
Recipients arjennienhuis, barry, benjamin.peterson, christian.heimes, durin42, ecir.hana, eric.smith, exarkun, ezio.melotti, flox, glyph, gregory.p.smith, gvanrossum, loewis, martin.panter,, pitrou, serhiy.storchaka, stendec, terry.reedy, uau, vstinner
Date 2013-10-08.22:20:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
On Oct 8, 2013, at 6:19 PM, Glyph Lefkowitz <> wrote:

> Glyph Lefkowitz added the comment:
> On Oct 8, 2013, at 2:35 PM, Eric V. Smith wrote:
>> What proposal is actually on the table here?
> Sorry Eric, you're right, there is too much discussion here.  This issue ought to be about .format, like the title says.  There should be a separate ticket for %-formatting, since it seems to be an almost wholly unrelated task.  While I'm sympathetic to Mercurial's issues, they're somewhat different from Twisted's, in that we're willing to adopt the "one new way" to do things in order to achieve compatibility whereas that would be too hard for Mercurial.

Yeah, my bad too. I suppose I should add a new bug for %-formatting on bytes objects?

Note that for hg, we can't drop Python 2.6 or so (we'll only drop *2.4* if we can do 2.6 and some 3.x from a single source tree) for a while, due to supporting the system interpreter on a variety of LTS platforms.
Date User Action Args
2013-10-08 22:20:50durin42setrecipients: + durin42, gvanrossum, loewis, barry, terry.reedy, gregory.p.smith, exarkun, pitrou, vstinner, eric.smith, christian.heimes, benjamin.peterson, glyph, ezio.melotti, arjennienhuis, flox, ecir.hana, uau, martin.panter, serhiy.storchaka,, stendec
2013-10-08 22:20:50durin42linkissue3982 messages
2013-10-08 22:20:50durin42create