Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on Understanding mutable default arguments in Python

Post

Understanding mutable default arguments in Python

+9
−0

Consider this code example:

def example(param=[]):
    param.append('value')
    print(param)

When example is repeatedly called with an existing list, it repeatedly appends to the list, as one might expect:

>>> my_list = []
>>> example(my_list)
['value']
>>> example(my_list)
['value', 'value']
>>> example(my_list)
['value', 'value', 'value']
>>> my_list
['value', 'value', 'value']
If it's called with an empty list each time, it seems that each empty list is considered separately, which also makes sense:
>>> example([])
['value']
>>> example([])
['value']
>>> example([])
['value']
However, if called without passing an argument - using the default - it seems to "accumulate" the appended values as if the same list were being reused:
>>> example()
['value']
>>> example()
['value', 'value']
>>> example()
['value', 'value', 'value']

Some IDEs will warn that param is a "mutable default argument" and suggest changes.

Exactly what does "mutable default argument" mean, and what are the consequences of defining param this way? How is this functionality implemented, and what is the design decision behind it? Is it ever useful? How can I avoid bugs caused this way - in particular, how can I make the function work with a new list each time?

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

2 comment threads

TODO (1 comment)
Split question (1 comment)
TODO
Karl Knechtel‭ wrote about 1 year ago · edited about 1 year ago

I want to split this up so that there is a separate question for the workarounds. It feels a bit shoehorned in here, especially since the underlying problem (early binding of defaults) has other effects (e.g. not supporting a default parameter "based on" another parameter).

Also, I plan to have a separate Q&A to explain and justify the concept of command-query separation, which will allow factoring out some more content from my first attempt at answers here.

Skipping 1 deleted comment.