Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 619731
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 13, 20262026-05-13T18:41:13+00:00 2026-05-13T18:41:13+00:00

I might be missing something about the intended behavior of list extend, but why

  • 0

I might be missing something about the intended behavior of list extend, but why does the following happen?

x = [[],[]]
y = [[]] * 2

print x       # [[],[]]
print y       # [[],[]]
print x == y  # True

x[0].extend([1])
y[0].extend([1])

print x    # [[1],[]], which is what I'd expect
print y    # [[1],[1]], wtf?

I would guess that the * operator is doing something unexpected here, though I’m not exactly sure what. It seems like something is going on under the hood that’s making the original x and y (prior to calling extend) not actually be equal even though the == operator and repr both would make it seem as though they were identical.

I only came across this because I wanted to pre-populate a list of empty lists of a size determined at runtime, and then realized that it wasn’t working the way I imagined. I can find a better way to do the same thing, but now I’m curious as to why this didn’t work. This is Python 2.5.2 BTW – I don’t have a newer version installed so if this is a bug I’m not sure if it’s already fixed.

  • 1 1 Answer
  • 3 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-13T18:41:14+00:00Added an answer on May 13, 2026 at 6:41 pm

    In the case of [something] * 2, python is simply making a reference-copy. Therefore, if the enclosed type(s) are mutable, changing them will be reflected anywhere the item is referenced.

    In your example, y[0] and y[1] point to the same enclosed list object. You can verify this by doing y[0] is y[1] or alternately id(y[0]) == id(y[1]).

    You can however re-assign list elements, so if you had done:

    y[0] = [1]
    

    You would’ve re-bound the first element to a new list containing the element “1”, and you would’ve got your expected result.

    Containers in python store references, and it’s possible in most sequence containers to reference the same item multiple times. A list can actually reference itself as an element, though the usefulness of this is limited.

    This issue wouldn’t have come up if you had multiplied a list containing immutable types:

    a = [0, 1] * 2
    

    The above would give you the list [0, 1, 0, 1] and indeed both instances of 1 point to the same object, but since they are immutable, you cannot change the value of the int object containing “1”, only reassign elements.

    So doing: a[1] = 5 would result in a showing as [0, 5, 0, 1].

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I might be missing something obvious but is there a reference somewhere about what
I might be missing something here but am unable to understand the true purpose
I might be missing something obvious here, but I'm implementing NSCopying on one of
I might be missing something but how do you manage Java projects in eclipse
I think I might be missing something, but I can't see how to use
I might be missing something really obvious. I'm trying to write a custom Panel
I may be missing something here because I thought this might be really easy
Might be a bit of noob question but it's something that's been getting me
All, I am missing something fundamental about the underlying model for Django's ForeingKeys vs
Since I'm not a native English speaker I might be missing something so maybe

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.