raymond hettinger jebpthrcncom terry reedy people write somename lambda args expression instead obvious people dare say standard def somenameargs return expression though defstatements usually best way go reasonable cases first form reads better say leave programmer decide experience quickly teach defstatement flexible another thought often give advice longline becomes hard read easy solution pullout inner expression give name especially true intended purpose inner expression isnt obvious giving name adds clarity would burden advice admonition go move relevant code farther away used kg groupbyiterable keylambda r r0lower r5lower lastname_firstname lambda r r0lower r5lower k g groupbyiterable keylastname_firstname transformation adds clarity going creating separate defstatement outside current function would move relevant code farther away impair readability also im somewhat opposed using pep 8 way somehow peps recommendations seem get occasionally interpreted law imo pep limited things real impact code maintained multiple programmers grow general purpose set situation independent prejudgments constructs favored others ie programmer x hates forelse avoided favor using flags programmer thinks uncool returnstatement anywhere end function style mavens think 1 raymond _______________________________________________ pythondev mailing list zvlllneumpythonorg httpmailpythonorgmailmanlistinfopythondev unsubscribe httpmailpythonorgmailmanoptionspythondevpythondev40tangomucom fri 08 aug 2008 030527 0700 pythondev pep 8 discourage named lambdas