![](https://secure.gravatar.com/avatar/15c3eef50a943fdefa0cb50a21d11203.jpg?s=120&d=mm&r=g)
Thanks to everyone who provided feedback about an override decorator in last week’s meetup! We have finished an initial draft proposal [1]. We’re happy to take comments and suggestions on this doc; we also looking for a sponsor so we can put a PR together. We also specifically wanted to call out some edge cases that might be worth addressing in the “Specification” section related to how override interacts with regular attributes. The main override-specific question is whether we care about a way to mark attribute assignments as overrides, since they are subject to the same renaming bugs. But that brings up a few more edge cases such as properties and methods that override attributes. We’ve drawn up a doc [2] highlighting all these edge cases and would love to hear feedback. - Joshua Xu and Steven Troxler ------------------ [1] Draft PEP for @typing.override https://docs.google.com/document/d/1dBkHKaOCqttnqzPo7kw1dzvbuFzNoOdx7OPyfbJH... [2] Edge cases related to attributes https://docs.google.com/document/d/1dhlcKKuYtGN9Eftr1hu9U6EKzsS0NPuQm01b7brj... [3] Slides from last week's presentation https://drive.google.com/drive/folders/1sGZ0WBLaVBkCb0AT7tneCEwbATxgisI2 [4] Original thread regarding override https://mail.python.org/archives/list/typing-sig@python.org/thread/V23I4D6DE...