Python Slice Assignment Memory Usage

后端 未结 1 693
名媛妹妹
名媛妹妹 2020-11-28 09:32

I read in a comment here on Stack Overflow that it is more memory efficient to do slice assignment when changing lists. For example,

a[:] = [i + 6 for i in          


        
相关标签:
1条回答
  • 2020-11-28 10:15

    The line

    a[:] = [i + 6 for i in a]
    

    would not save any memory. Python does evaluate the right hand side first, as stated in the language documentation:

    An assignment statement evaluates the expression list (remember that this can be a single expression or a comma-separated list, the latter yielding a tuple) and assigns the single resulting object to each of the target lists, from left to right.

    In the case at hand, the single resulting object would be a new list, and the single target in the target list would be a[:].

    We could replace the list comprehension by a generator expression:

    a[:] = (i + 6 for i in a)
    

    Now, the right hand side evaluates to a generator instead of a list. Benchmarking shows that this is still slower than the naive

    a = [i + 6 for i in a]
    

    So does the generator expression actually save any memory? At first glance, you might think it does. But delving in to the source code of the function list_ass_slice() shows that it does not. The line

    v_as_SF = PySequence_Fast(v, "can only assign an iterable");
    

    uses PySequence_Fast() to convert the iterable (in this case the generator) into a tuple first, which is then copied into the old list. A tuple uses the same amount of memory as a list, so using a generator expression is basically the same as using a list comprehension in this case. During the last copy, the items of the original list are reused.

    The moral seems to be that the simplest approach is the best one in any regard.

    0 讨论(0)
提交回复
热议问题