Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed6.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
Date: Thu, 17 Nov 2011 19:01:01 -0800
From: Dominic Binks <dbinks@codeaurora.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: python-list@python.org
Subject: Re: What exactly is "pass"? What should it be?
References: <27955957.352.1321582691251.JavaMail.geo-discussion-forums@prap37> <CAMZYqRREhvpgv18QqxFjeE438LyLhO6cdzipFL+aVdVGLiKy8g@mail.gmail.com>
In-Reply-To: <CAMZYqRREhvpgv18QqxFjeE438LyLhO6cdzipFL+aVdVGLiKy8g@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.2815.1321585339.27778.python-list@python.org>
Lines: 68
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:15852

On 11/17/2011 6:45 PM, Chris Rebert wrote:
> On Thu, Nov 17, 2011 at 6:18 PM, John Ladasky<ladasky@my-deja.com>  wrote:
>> Hi folks,
>>
>> I'm trying to write tidy, modular code which includes a long-running process.  From time to time I MIGHT like to check in on the progress being made by that long-running process, in various ways.  Other times, I'll just want to let it run.  So I have a section of code which, generally, looks like this:
>>
>> def _pass(*args):
>>     pass
>>
>> def long_running_process(arg1, arg2, arg_etc, report = _pass):
>>     result1 = do_stuff()
>>     report(result1)
>>     result2 = do_some_different_stuff()
>>     report(result2)
>>     result3 = do_even_more_stuff()
>>     report(result3)
>>     return result3
>>
>> This does what I want.  When I do not specify a report function, the process simply runs.  Typically, when I do supply a report function, it would print something to stdout, or draw an update through a GUI.
>>
>> But this approach seems a tad cumbersome and unPythonic to me, particularly the part where I define the function _pass() which accepts an arbitrary argument list, and does nothing but... pass.
>
> Seems fine to me (good use of the null object pattern), although I
> might define _pass() to instead take exactly 1 argument, since that's
> all you ever call report() with in your example.
>
>> This has led me to ask the question, what exactly IS pass?  I played with the interpreter a bit.
>>
>> IDLE 2.6.6      ==== No Subprocess ====
>>>>> pass
>>>>> pass()
>> SyntaxError: invalid syntax
>>>>> type(pass)
>> SyntaxError: invalid syntax
>>
>> So, pass does not appear to be a function, nor even an object.  Is it nothing more than a key word?
>
It is a keyword that can appear in a position where a statement is 
required by the grammar but there is nothing to do.  For example if .. 
then .. else .. where nothing happens in the else condition is effectively:

   if <condition>:
  	<then-part>
   else:
	pass

Bourne shell has a similar construct with the colon statement :

Another python example is where you need to catch an exception (or all 
exceptions but don't actually care about what they are)

   try:
      <european swallows>
   except:
      pass

> Correct:
> http://docs.python.org/reference/simple_stmts.html#pass
> http://docs.python.org/reference/lexical_analysis.html#keywords
>
> Cheers,
> Chris


-- 
Dominic Binks: dbinks@codeaurora.org
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum