On Thu, Sep 13, 2018 at 5:34 PM Anders Hovmöller <bo...@killingar.net> wrote:
> I wrote a script so you can get a list of [good use cases] in big code > bases without looking through the code randomly. > https://gist.github.com/boxed/e60e3e19967385dc2c7f0de483723502 > In that case, you should be able to link to a compelling example. If you go to the trouble of finding one, I'll take time to try to refactor it. Let’s not exaggerate [the pain of implementation]. > The pain is not just time to implement, but also code review, more surface area for bugs, increased maintenance burden, and teaching users about the new feature. We aren’t optimizing for not changing the language just to make people not > learn new things. > On the contrary, I think we should be. Ceteris paribus, it's not good to churn the language. It's not some startup hoping to find a business model. The more techniques available, the less consistent Pythonic style will be. There are always trade-offs. In this case, I don't think the benefit is worth the cost.
_______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
