Direct links to the PEPs themselves, to perhaps save others a little time.<p>Accepted:<p><i>Specification</i> <a href="https://www.python.org/dev/peps/pep-0634/" rel="nofollow">https://www.python.org/dev/peps/pep-0634/</a><p><i>Motivation and Rationale</i> <a href="https://www.python.org/dev/peps/pep-0635/" rel="nofollow">https://www.python.org/dev/peps/pep-0635/</a><p><i>Tutorial</i> <a href="https://www.python.org/dev/peps/pep-0636/" rel="nofollow">https://www.python.org/dev/peps/pep-0636/</a><p>Rejected:<p><i>Unused variable syntax</i> <a href="https://www.python.org/dev/peps/pep-0640/" rel="nofollow">https://www.python.org/dev/peps/pep-0640/</a><p><i>Explicit Pattern Syntax for Structural Pattern Matching</i> <a href="https://www.python.org/dev/peps/pep-0642/" rel="nofollow">https://www.python.org/dev/peps/pep-0642/</a>
It's interesting that pattern matching has been accepted despite a poll showing a majority (65%) of core developers opposed to this particular proposal, and a plurality (44%) opposed to pattern matching altogether.<p><a href="https://discuss.python.org/t/gauging-sentiment-on-pattern-matching/5770" rel="nofollow">https://discuss.python.org/t/gauging-sentiment-on-pattern-ma...</a>
Is it still the case that these two pieces of code have different behaviour?<p><pre><code> match status:
case 404:
return "Not found"
not_found = 404
match status:
case not_found:
return "Not found"
</code></pre>
IIRC in an earlier proposal, the former would check for equality (`status == 404`) and the latter would perform an assignment (`not_found = status`).