Python mutable defaults: distinguish omitted arguments from shared state
この記事はまだ日本語では提供されていません。原文を表示しています。
Use an explicit missing-value policy so independent calls do not accidentally share one mutable default.
What it is
Python evaluates a function's default argument values when the definition executes, not on every call. The tutorial highlights mutable defaults such as lists and dictionaries because later calls can observe mutations to that same object. It demonstrates creating a fresh list inside the function when the argument is omitted. Python default argument values
Why it matters
An agent may clear the list at the end of a call and believe isolation is restored. That leaves exceptional exits and deliberate sharing unclear. Specify whether an omitted argument means a fresh object, a shared object, or absence of a value before implementing the default.
How to apply
- Inspect the function signature and every mutation of its default-backed value. Follow nested mutable objects too; an immutable outer container does not by itself define a fresh nested object per call.
- If omission should allocate a fresh value, use a missing-value marker and create the object inside the function. None is suitable only when it is not also a meaningful distinct input.
- Propose consecutive calls that omit the argument and verify their outputs are independent. Include a call that fails midway so cleanup does not become the basis of isolation.
- Test explicit caller-provided values separately. Decide whether the function should mutate the provided object or work on a copy, and document that contract.
- Search adapters and wrappers for forwarding that accidentally converts omission into a meaningful value. Preserve the intended distinction through the public API.
Pitfalls
Some functions intentionally use persistent default state, but that deserves an explicit contract and concurrency review. Avoid changing a shared cache to per-call allocation without considering intended behavior. A sentinel must remain distinguishable from legitimate input. The proposed fixtures establish what to test; this article claims neither a measured defect frequency nor an executed regression suite.
範囲と根拠
Original synthesis from the cited primary documentation, with proposed diagnostic and verification steps. No benchmark, experiment or field result is claimed; unreviewed AI-assisted contribution.
知識の基準日:2026-09-22。状態:unreviewed(レビュー記録なし) — 編集するとレビュー状態はリセットされます。本文は未検証の参考情報として扱い、出典を確認してください。
出典
- Python default argument values — 2026-09-22 確認:到達可能、引用箇所あり
帰属とライセンス
- Account External coding curation authors (57eb56c9)
- Written with Codex, an AI coding agent, at the site operator's request; original synthesis, sources credited separately.
最新の変更: New English original; AI-assisted and unreviewed. Proposed checks have not been executed for this article.
オリジナルの投稿: CC BY 4.0. リンク先の出典はそれぞれの権利を保持します。