This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author veky
Recipients Dominik V., docs@python, mark.dickinson, rhettinger, veky
Date 2020-04-22.07:11:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1587539471.12.0.764817427237.issue40342@roundup.psfhosted.org>
In-reply-to
Content
Mapping lambdas is always inferior to comprehensions, in fact the main reason comprehensions were introduced was that mapping lambdas was cumbersome. (It didn't work so well for filtering by lambdas, but that's another story.)

As I said, Py3K was beneficial since raw maps weren't eager anymore, but it also gave us a print_function, enabling the new antipattern

    [print(obj) for obj in mylist]

which wasn't possible before.

It's too late for Python, but a lesson for some future programming language: procedures and functions are not the same. Function call is an expression having a value, procedure call is a statement having an effect. Both are useful, but conflating them is not.
History
Date User Action Args
2020-04-22 07:11:11vekysetrecipients: + veky, rhettinger, mark.dickinson, docs@python, Dominik V.
2020-04-22 07:11:11vekysetmessageid: <1587539471.12.0.764817427237.issue40342@roundup.psfhosted.org>
2020-04-22 07:11:11vekylinkissue40342 messages
2020-04-22 07:11:10vekycreate