Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.003 X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'attribute': 0.07; 'level,': 0.07; 'responding': 0.07; 'ambiguity': 0.09; 'bits': 0.09; 'expectation': 0.09; 'prefix': 0.09; 'spelling': 0.09; 'structure,': 0.09; 'subject:Function': 0.09; 'cc:addr:python- list': 0.11; 'def': 0.12; 'wrote': 0.14; 'thread': 0.14; "wouldn't": 0.14; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'function?': 0.16; 'tuple': 0.16; 'unambiguous': 0.16; 'followed': 0.16; 'wrote:': 0.18; 'bit': 0.19; 'thu,': 0.19; 'meant': 0.20; 'separate': 0.22; 'cc:addr:python.org': 0.22; 'error': 0.23; '(by': 0.24; 'certainly': 0.24; 'copied': 0.24; 'effort.': 0.24; 'helpful': 0.24; 'looks': 0.24; 'cc:2**0': 0.24; 'this:': 0.26; 'post': 0.26; 'header:In-Reply-To:1': 0.27; 'idea': 0.28; 'am,': 0.29; "doesn't": 0.30; 'heading': 0.30; 'message- id:@mail.gmail.com': 0.30; 'code': 0.31; 'getting': 0.31; 'lines': 0.31; 'reply.': 0.31; 'indentation': 0.31; 'piece': 0.31; 'post.': 0.31; 'covered': 0.32; 'alone': 0.33; 'fri,': 0.33; 'something': 0.35; 'case,': 0.35; 'but': 0.35; 'received:google.com': 0.35; 'there': 0.35; 'really': 0.36; 'words,': 0.36; 'yield': 0.36; 'done': 0.36; "didn't": 0.36; 'should': 0.36; 'too': 0.37; 'two': 0.37; 'clear': 0.37; 'easily': 0.37; 'being': 0.38; 'expected': 0.38; 'pm,': 0.38; 'that,': 0.38; 'little': 0.38; 'called': 0.40; 'even': 0.60; "you're": 0.61; 'complete': 0.62; 'real': 0.63; 'more': 0.64; 'between': 0.67; 'subject': 0.69; 'led': 0.72; 'honest': 0.78; 'compare:': 0.84; 'distinguish': 0.84; 'hard.': 0.84; 'malicious': 0.84; 'this...': 0.84; 'to:none': 0.92 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type; bh=PwlQKj4VCpHEwDAq7hU8ev6qHZ11cnQVNxSEiY/+xSA=; b=Luz7qax9B3/s+uoYaUZuPKa1TxmVT6u9ZKoAThVRe/lWMe20u9gUsN14yEt+CB7qLE vIpHD/yX1woDVR5xqohzh/DAFlpiZTPcywPN9s5BeTIWW/KN2ttPdKfmndlSzWmd42gM G5yBNtDVKYf/smLoRA60q0IV8vu0hi740lg15ZgXPFcs8xS70j4QdEJHDneh8A4KnPVx zjy8pweihIcco4dMIAp0dJ8e0RXhVgktssxfC6OAZv6ncGTJUtB6jsMUPcvqO8lku+KT okJowe3rDVB0AGCjZ/9uW5nTVRdNMtCi3NWrb9tJwAjHc+ucelWFjsjPfsi9RY9ncr1j FtLw== MIME-Version: 1.0 X-Received: by 10.50.66.234 with SMTP id i10mr10257528igt.34.1412302116968; Thu, 02 Oct 2014 19:08:36 -0700 (PDT) In-Reply-To: References: <6bf1fc74-e40f-41f0-88b9-e4543c731e69@googlegroups.com> <542d05f7$0$12998$c3e8da3$5496439d@news.astraweb.com> <0aaba2f6-dfa4-4ec1-9460-a97c65f2e0eb@googlegroups.com> <542de98e$0$12981$c3e8da3$5496439d@news.astraweb.com> Date: Fri, 3 Oct 2014 12:08:36 +1000 Subject: Re: Function passed as an argument returns none From: Chris Angelico Cc: "python-list@python.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 66 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1412302126 news.xs4all.nl 2873 [2001:888:2000:d::a6]:36097 X-Complaints-To: abuse@xs4all.nl Path: csiph.com!usenet.pasdenom.info!bete-des-vosges.org!feed.ac-versailles.fr!nerim.net!novso.com!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Xref: csiph.com comp.lang.python:78632 On Fri, Oct 3, 2014 at 11:49 AM, Rustom Mody wrote: > Ok so there is no conventional attribution line because it was > cut-pasted from elsewhere in the thread but there is a clear > and unequivocal prefix of "OP subject as well as post". When I respond to this part... > Why/how should there be any ambiguity that that is Shiva?? ... and then to this, the normal assumption is that, since both are at the same indentation level, they're both covered by the same heading line. Compare: def rustom(): yield "... there is no conventional ..." yield "... elsewhere in the thread ..." yield "... unequivocal ..." # I respond to this... yield "... any ambiguity ..." # Is there any expectation that the above line of code isn't part of the same function? And there IS an unequivocal prefix of "OP subject as well as post". It looks like this: On Thu, Oct 2, 2014 at 8:37 AM, Shiva wrote: > Any idea why 'None' is getting passed even though calling the donuts(4) > alone returns the expected value? And there's even an unambiguous way to indicate that you're responding to the original poster, but not the original post. Watch! On Thu, Oct 2, 2014 at 6:46 PM, Shiva wrote: > * return 'Number of donuts: ',count returns a tuple like: > ('Number of donuts: ',9) I can correctly attribute every piece that I respond to. It's really not hard. In this particular case, I opened two additional replies, and copied and pasted the bits I want into this reply. Some people short-cut it, when they're responding to separate posts, and just do something like this: [Rustom Mode] > Are you for real Steven?? Complete with a demonstration of what happens all too often when things are done manually: a spelling error in the attribution line. It's still unambiguous as to who wrote what, though a little less helpful as regards chronology. Attribution lines are part of being honest about who said what. I wouldn't say that your post was evidence of malicious intent, but it was sloppiness that led to an easily misunderstood post. On rereading, I can see that you did try to indicate (by your text) that it was meant to be followed by the OP's words, but you didn't put that into the structure, and you certainly didn't distinguish between the original post and the one made a little bit later. Please, if you don't want to be called out for misattribution, just be a bit more careful. It doesn't take a huge amount of effort. ChrisA