Sorry, -1. Is this really worth the hassle when you can write (more explicitly) def my_fun(): raise NotImplementedError # todo Python has grown steadily more complicated in its lifetime. Usually for good reasons. But each additional feature adds to the learning curve and the maintenance burden. New features have to be justified by getting a consensus that the benefits outweigh the extra complexity. How would you decide what corner cases such as these would do: eval("...") exec("...") [ ... ][0] ... if x is None else y return ... and how would this affect the implementation of the compiler/interpreter? Best wishes Rob Cliffe On 27/04/2023 14:45, haael wrote:
In examples in the web very often we see unfinished or partial code, where the ellipsis "..." is used in place of missing instructions.
Idea: make ellipsis used in that context throw an exception, reminding the user that this code is work in progress.
The exception could be called ToDoError, or WorkInProgressError, or simply EllipsisError, and could be derived from NotImplementedError.
```
def my_fun(): ... # todo
my_fun()
WorkInProgressError: Implementation of `my_fun` is not finished.
```
This change could break some code, as for now ellipsis in the middle of code is silently ignored, but I don't think anybody seriously relies on that behavior.
haael
_______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-leave@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/QAU7LB... Code of Conduct: http://python.org/psf/codeofconduct/