# PEP 8012: Frequently Asked Questions

**URL:** https://discuss.python.org/t/pep-8012-frequently-asked-questions/487
**Category:** Committers
**Tags:** governance
**Created:** [November 27, 2018, 2:30pm UTC](https://discuss.python.org/t/pep-8012-frequently-asked-questions/487 "2018-11-27T14:30:56Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![guido](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/guido/32/21_2.png) [@guido](https://discuss.python.org/u/guido)
#### Post date: [November 27, 2018, 5:37pm UTC](https://discuss.python.org/t/pep-8012-frequently-asked-questions/487/2 "2018-11-27T17:37:27Z")

</div>

> [@ambv](#):
>
> #### Will this slow down radical changes to Python?
> 
> Yes, controversial ones. That’s not the worst thing to happen to a 30-year-old language, is it?

(Sorry if this is a repeat of past discussions. I’ve been ignoring this thing to ward off recurring feelings of burn-out.)

This worries me though. While I understand this is meant to avoid another drama like assignment expressions, it would also prevent something as useful as decorators to be added to the language, and very likely it would end up blocking adding a `match` statement (there’s just no way we can make `match` a keyword, there are no other reasonable candidate keywords, and solutions like `@match` or `$match` would be too controversial). Essentially the language would stop evolving. I worry that that would make Python become the next legacy language rather than the language that everyone wants to use.

---

_[View the full topic](https://discuss.python.org/t/pep-8012-frequently-asked-questions/487)._