Thanks for your response. While legacy production code is always an issue with 
potentially breaking changes, this line of thought would mean that future 
versions of Python could never introduce breaking changes. This should not be 
the case and is not the case now: for new Python versions, developers are 
expected to test and check for breaking changes, not just update production 
environments to a new version and hope for the best. The fact that this would 
throw an error instead of the expected empty list should then quickly lead to 
the right solution, whereas the other way around, when you expect an error but 
get an empty list, is hard to debug. That is a tradeoff with a clear winner in 
my opinion.
_______________________________________________
Python-ideas mailing list -- python-ideas@python.org
To unsubscribe send an email to python-ideas-le...@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/IZORCHR4TZLKNSTPM3SKHIVT2K34F5H3/
Code of Conduct: http://python.org/psf/codeofconduct/

Reply via email to