[RUF008] Make it clearer that a mutable default in a dataclass is only valid if it is typed as a ClassVar #10395
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
The previous documentation sounded as if typing a mutable default as a
ClassVar
were optional. However, it is not, as not doing so causes aValueError
. The snippet below was tested in Python's interactive shell:This behavior is also documented in Python's docs, see here:
And here it is documented why it works if it is typed as a
ClassVar
:In this PR I have changed the documentation to make it a little bit clearer that not using
ClassVar
makes the code invalid.