Augie Fackler added the comment: On Oct 8, 2013, at 6:19 PM, Glyph Lefkowitz <rep...@bugs.python.org> 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue3982> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
