Clarification: interaction between `@property` and `@final`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.8k
- Forks
- 302
- Avg merge
- 23h
- Merged PRs (30d)
- 8
Description
The spec for @final says:
The method decorator version may be used with all of instance methods, class methods, static methods, and properties.
and it made me wonder how exactly final interacts with property. There are no conformance tests exercising this specific interaction.
From carefully reading the spec, it seems like the only effect of @final on a property is to prevent it from being overridden in a child class, and that decorating a property with @final does not cause it to be read-only or disallow a setter.
Is my understanding correct? If so, does it make sense to add a clarification to the spec that the decorator does not make a property read-only?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the @final section of the typing specification and review existing conformance tests for properties, setters, and inheritance. Done means the specification clearly states how @final applies to properties and, if appropriate, a conformance test records the intended behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation, testing-qa
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100