from future import pass_function

Mark Lawrence breamoreboy at
Thu Jul 26 09:43:48 CEST 2012

On 26/07/2012 05:03, Ross Ridge wrote:
> Ross Ridge <rridge at> wrote:
>> No, they're very much alike.  That's why all your arguments for print
>> as function also apply just as well to pass a function.  Your arguments
>> had very little to do what what print actually did.
> Chris Angelico  <rosuav at> wrote:
>> Except that print / print() is executable. Execution proceeds through
>> your code, comes to a "print", and goes off to handle that, then comes
>> back to your code. But "pass" doesn't have code attached to it. Why
>> should it be a function?
> For consistancy with print.  What it does doesn't matter any more than
> what print did mattered.
> 					Ross Ridge

My all time favourite engineering quote, from the UK Ptarmigan tactical 
communications project, springs to my mind here regarding your comments 
about the comparison of print and pass.  "I might not be a mechanical 
engineer, but that's fucking wrong".


Mark Lawrence.

More information about the Python-list mailing list