On Sun, Apr 19, 2020 at 11:18 PM David Mertz <me...@gnosis.cx> wrote:
> If this were in the library I or my project used, whatever limitations and > edge cases exist wouldn't really matter. If I REALLY cared about saving a > few duplicate names in function calls, I could easily include it with the > knowledge that it won't handle such-and-such edge cases. > No you couldn't, it would cause untold pain to anyone who collaborated with you (or even just your future self) who didn't know which edge cases it can't handle and that they have to tiptoe around it. "David this code breaks when I spread it out across multiple lines" "David this code breaks when I collapse it into one line" "David this code breaks when I rename a function" "David this code breaks when I paste it into a shell" "David I really like this M function, i've been using it for debugging like print(M(foo, bar)), but when I changed the line make_payment() to print(M(make_payment())) it made the payment twice"
_______________________________________________ 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/ALD3BFAW3QGCHVJ5DFXFAZGCI3DWAIYH/ Code of Conduct: http://python.org/psf/codeofconduct/
