Databases
StackOverflow2013
Postsdbo
POSpeed vs security vs compatibility over methods to do string concatenation in Python
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSpeed vs security vs compatibility over methods to do string concatenation in Python
    primarykey
    data
    text
    <p><a href="https://stackoverflow.com/questions/1225637/python-string-formatting">Similar</a> questions <a href="https://stackoverflow.com/questions/376461/string-concatenation-vs-string-substitution-in-python/376508#376508">have been brought</a> (good speed comparison there) on this same <a href="http://en.wikipedia.org/wiki/Concatenation" rel="nofollow noreferrer">subject</a>. Hopefully this question is different and updated to Python <em>2.6</em> and <em>3.0</em>.</p> <p>So far I believe the faster and most compatible method (among different Python versions) is the plain simple <code>+</code> sign:</p> <pre><code>text = "whatever" + " you " + SAY </code></pre> <p>But I keep hearing and reading it's not secure and / or advisable.</p> <p>I'm not even sure how many methods are there to manipulate strings! I could count only about 4: There's <a href="http://en.wikipedia.org/wiki/Variable_interpolation#Interpolation" rel="nofollow noreferrer">interpolation</a> and all its sub-options such as <code>%</code> and <code>format</code> and then there's the simple ones, <code>join</code> and <code>+</code>.</p> <p>Finally, the <a href="http://docs.python.org/release/3.0.1/whatsnew/3.0.html#pep-3101-a-new-approach-to-string-formatting" rel="nofollow noreferrer">new approach to string formatting</a>, which is with <code>format</code>, is certainly not good for backwards compatibility at same time making <code>%</code> not good for forward compatibility. But should it be used for every string manipulation, including every concatenation, whenever we restrict ourselves to 3.x only?</p> <p>Well, maybe this is more of a wiki than a question, but I do wish to have an answer on <strong>which is the proper usage of each string manipulation method</strong>. And which one could be generally used with each focus in mind (best all around for compatibility, for speed and for security).</p> <p>Thanks.</p> <p>edit: I'm not sure I should accept an answer if I don't feel it really answers the question... But my point is that all them 3 together do a proper job.</p> <p>Daniel's most voted answer is actually the one I'd prefer for accepting, if not for the "note". I highly disagree with <em>"concatenation is strictly using the + operator to concatenate strings"</em> because, for one, <code>join</code> does string concatenation as well, and we can build any arbitrary library for that.</p> <p><strong>All current 3 answers are valuable</strong> and I'd rather having some answer mixing them all. While nobody volunteer to do that, I guess by choosing the one less voted (but fairly broader than THC4k's, which is more like a large and very welcomed comment) I can draw attention to the others as well.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. UScregox
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSpeed vs security vs compatibility over methods to do string concatenation in Python
      1. USunutbu
      1. VTFavorite
    2. VO
      singulars
      1. POSpeed vs security vs compatibility over methods to do string concatenation in Python
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POSpeed vs security vs compatibility over methods to do string concatenation in Python
      1. USBolo
      1. VTFavorite
    1. COWhere are you reading that `+` is "not secure and / or advisable"?
      singulars
      1. POSpeed vs security vs compatibility over methods to do string concatenation in Python
      1. USJohn Machin
    2. CO@John for one, read the 2 answers below. They both discourage using `+`.
      singulars
      1. POSpeed vs security vs compatibility over methods to do string concatenation in Python
      1. UScregox
    3. COPerhaps I was interpreting 'advisable' differently to you. In any case you wrote that before the answers were written. Also neither of the answers point out that `+=` has been made faster in more recent Pythons. Where are you reading that `+` is "not secure"?
      singulars
      1. POSpeed vs security vs compatibility over methods to do string concatenation in Python
      1. USJohn Machin
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload