➜

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 glyph
Recipients arjennienhuis, benjamin.peterson, christian.heimes, eric.smith, exarkun, ezio.melotti, flox, glyph, gvanrossum, loewis, martin.panter, pitrou, serhiy.storchaka, terry.reedy, uau, vstinner
Date 2013-01-23.18:58:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <4228CBE4-155D-4A06-92F8-19726542293B@twistedmatrix.com>
In-reply-to <1358926279.28.0.299507836287.issue3982@psf.upfronthosting.co.za>
Content 
On Jan 22, 2013, at 11:31 PM, Martin v. Löwis <report@bugs.python.org> wrote:

> I admit that it is puzzling that string interpolation is apparently the fastest way to assemble byte strings. It involves parsing the format string, so it ought to be slower than anything that merely concatenates (such as cStringIO). (I do understand why + is inefficient, as it creates temporary objects)

You're correct about this; see my previous comment.
History
Date User Action Args
2013-01-23 18:58:21glyphsetrecipients: + glyph, gvanrossum, loewis, terry.reedy, exarkun, pitrou, vstinner, eric.smith, christian.heimes, benjamin.peterson, ezio.melotti, arjennienhuis, flox, uau, martin.panter, serhiy.storchaka
2013-01-23 18:58:20glyphlinkissue3982 messages
2013-01-23 18:58:20glyphcreate