[issue1569040] Speed up using + for string concatenation

Benjamin Peterson added the comment: This issue hasn't been touched in years and would certainly need a completely new patch. -- resolution: -> rejected status: open -> closed ___ Python tracker ___

[issue1569040] Speed up using + for string concatenation

Ramchandra Apte added the comment: Buuump. -- nosy: +ramchandra.apte ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue1569040] Speed up using + for string concatenation

Larry Hastings added the comment: Thanks for pointing that out! I think I found it; the discussion is actually about lazy string slices, and it starts here: http://mail.python.org/pipermail/python-dev/2000-February/002317.html If I were to resubmit lazy string slices (which wouldn't be in this

[issue1569040] Speed up using + for string concatenation

Raymond Hettinger added the comment: I think lazy evaluation was discussed in the same thread. Either I or someone else suggested it and there was some issue because the string struct had long been exposed and people were accessing it directly. -- _

[issue1569040] Speed up using + for string concatenation

Larry Hastings added the comment: rhettinger: It's a bit unfair to paint the lazy string concatenation patch with the adjective "ropes", then point out ropes have been rejected many times. Lazy string concatenation objects are a form of specialized rope but they don't share the downsides of the

[issue1569040] Speed up using + for string concatenation

Raymond Hettinger added the comment: IIRC, this has already been rejected on python-dev in a number of discussions (check for "ropes" in the search). Also, Armin has long ago implemented some optimizations for string concatenation in a number of contexts. -- nosy: +rhettinger

[issue1569040] Speed up using + for string concatenation

Antoine Pitrou added the comment: For information, I haven't done any benchmarks, but the StringIO type in Python 3.1 should be very efficient for this kind of purposes. -- nosy: +pitrou ___ Python tracker _

[issue1569040] Speed up using + for string concatenation

Benjamin Peterson added the comment: In that case, I think it's probably ok to reopen until we have a more definite accept or reject. -- resolution: rejected -> status: closed -> open ___ Python tracker ___

[issue1569040] Speed up using + for string concatenation

Larry Hastings added the comment: I'm not saying that killing a two-year-old DOA patch is the wrong move--though I hold out hope that lazy string concatenation in CPython will yet happen. But you shouldn't kill this patch just because you think it has something to do with "string views"--it doe

[issue1569040] Speed up using + for string concatenation

Benjamin Peterson added the comment: I'm rejecting this because previous string "views" have been rejected. -- nosy: +benjamin.peterson resolution: -> rejected status: open -> closed ___ Python tracker

[issue1569040] Speed up using + for string concatenation

Daniel Diniz added the comment: IIRC, this was rejected as part of a larger string views proposal. Leaving open so that current performance optimizers can take a look at this :) -- nosy: +ajaksu2 priority: normal -> low type: -> performance versions: -Python 2.6 _