New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update of reasoning why there is no case statement #84614
Comments
The design and history FAQ (https://docs.python.org/dev/faq/design.html#why-isn-t-there-a-switch-or-case-statement-in-python) explains why there is no case statement referencing PEP-275(https://www.python.org/dev/peps/pep-0275/). For Python 3 there is, however, PEP-3103(https://www.python.org/dev/peps/pep-3103/) which rejected the proposal for a switch statement. |
What is your reasoning on referencing just one of the PEPs and not both of them? |
the statement initially said that there was _no consensus yet on how to do range tests_. This is not true because there is now a decision to not do range tests - that decision is only in PEP-3103 and not in PEP-275 (PEP-275 actually links to PEP-3103 to explain why it is rejected). My feeling is that putting two references complicates the goal of explaining it. |
Well, am not very convinced if consensus was reached on range tests so I will refrain for someone else's opinion as it is not as apparent to me yet. |
out of date (see discussion on PR). |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: