[issue40434] Update of reasoning why there is no case statement

[Joannah Nanjekye]

Joannah Nanjekye  added the comment:

> PEP 275 actually links to PEP 3103 to explain why it is rejected

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.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue40434] Update of reasoning why there is no case statement

[Ama Aje My Fren]

Ama Aje My Fren  added the comment:

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.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue40434] Update of reasoning why there is no case statement

[Joannah Nanjekye]

Joannah Nanjekye  added the comment:

What is your reasoning on referencing just  one of the PEPs and not both of 
them?

--
nosy: +nanjekyejoannah

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue40434] Update of reasoning why there is no case statement

[Ama Aje My Fren]

Change by Ama Aje My Fren :


--
type:  -> enhancement

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue40434] Update of reasoning why there is no case statement

[Ama Aje My Fren]

Change by Ama Aje My Fren :


--
keywords: +patch
pull_requests: +19110
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/19787

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue40434] Update of reasoning why there is no case statement

[Ama Aje My Fren]

New submission from Ama Aje My Fren :

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.

--
assignee: docs@python
components: Documentation
messages: 367633
nosy: amaajemyfren, docs@python
priority: normal
severity: normal
status: open
title: Update of reasoning why there is no case statement
versions: Python 3.7, Python 3.8, Python 3.9

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com