Re: Using map()

From	Ned Batchelder <ned@nedbatchelder.com>
Subject	Re: Using map()
Date	2014-11-16 19:24 -0500
References	<mailman.15896.1416169228.18130.python-list@python.org> <54693cc4$0$13000$c3e8da3$5496439d@news.astraweb.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.15924.1416183892.18130.python-list@python.org> (permalink)

Show all headers | View raw

On 11/16/14 7:09 PM, Steven D'Aprano wrote:
> Pavel Volkov wrote:
>
>> I checked my modules with pylint and saw the following warning:
>>
>> W: 25,29: Used builtin function 'map' (bad-builtin)
>>
>> Why is the use of map() discouraged?
>> It' such a useful thing.
>
> That's a bug in pylint. It's not a bad builtin, it is perfectly fine.
>
> Some people don't like map. Pay no attention to them.

Pylint isn't useful until you've tailored the messages.  Personally, I 
avoid map, but your usage may vary.  The pylint message that always 
irked me was:

     W0142: Used * or ** magic

"magic"? They're features of the language!  Meanwhile, it doesn't mind 
if you write multiply-inherited metaclasses....

-- 
Ned Batchelder, http://nedbatchelder.com

Thread

Using map() Pavel Volkov <sailor@lists.xtsubasa.org> - 2014-11-16 16:01 +0300
  Re: Using map() Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-11-17 11:09 +1100
    Re: Using map() Ned Batchelder <ned@nedbatchelder.com> - 2014-11-16 19:24 -0500
    Re: Using map() Chris Angelico <rosuav@gmail.com> - 2014-11-17 12:08 +1100
    Messages from code analysis tools (was: Using map()) Ben Finney <ben+python@benfinney.id.au> - 2014-11-17 12:21 +1100
    Re: Using map() Dan Stromberg <drsalists@gmail.com> - 2014-11-16 17:31 -0800
    Re: Messages from code analysis tools (was: Using map()) Chris Angelico <rosuav@gmail.com> - 2014-11-17 12:36 +1100
    Re: Messages from code analysis tools Ned Batchelder <ned@nedbatchelder.com> - 2014-11-16 20:49 -0500

csiph-web