[Python-ideas] Why is design-by-contracts not widely
2QdxY4RzWzUUiLuE at potatochowder.com
Fri Sep 28 20:48:29 EDT 2018
On 9/28/18 8:32 PM, Chris Angelico wrote:
> On Sat, Sep 29, 2018 at 10:22 AM Dan Sommers
> <2QdxY4RzWzUUiLuE at potatochowder.com> wrote:
>> On 9/28/18 7:39 PM, Steven D'Aprano wrote:
>>> But none of that compares to C undefined behaviour. People who think
>>> that they are equivalent, don't understand C undefined behaviour.
>> Well, yes: Some syntactically legal C results in nasal demons, and some
>> of that code is harder to spot than others. AFAIK, syntactically legal
>> Python can only do that if the underlying C code invokes undefined
> What should happen here?
[examples of what Steven would call non-sensible, non-non-weird objects
doing non-non-weird things snipped]
AFAIK, "AFAIK" is a weasel word: It allows me to proclaim my own
ignorance without providing further examples, evidence, or counter
> Python has its own set of "well don't do that then" situations. In
> fact, I would say that *most* languages do.
More information about the Python-ideas