Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!newsfeed.xs4all.nl!newsfeed4a.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.009 X-Spam-Evidence: '*H*': 0.98; '*S*': 0.00; 'interpreter': 0.05; 'subject:Python': 0.06; 'subject:help': 0.08; 'exception.': 0.09; 'lines.': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'python': 0.11; 'discussion.': 0.16; 'finney': 0.16; 'i\xe2\x80\x99m': 0.16; 'quoted': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'wraps': 0.16; 'discussions': 0.16; 'do,': 0.16; 'trying': 0.19; 'community.': 0.22; 'header :User-Agent:1': 0.23; 'error': 0.23; '(such': 0.24; 'text.': 0.24; "haven't": 0.24; 'asking': 0.27; 'header:X-Complaints-To:1': 0.27; 'character': 0.29; "doesn't": 0.30; 'code': 0.31; 'url:wiki': 0.31; 'raised': 0.31; 'url:wikipedia': 0.31; 'writes:': 0.31; 'this.': 0.32; 'another': 0.32; 'subject:with': 0.35; 'received:com.au': 0.36; 'material': 0.36; 'shows': 0.36; 'thanks': 0.36; 'subject:?': 0.36; 'url:org': 0.36; 'turn': 0.37; 'expected': 0.38; 'ben': 0.38; 'to:addr:python-list': 0.38; 'anything': 0.39; 'to:addr:python.org': 0.39; 'received:org': 0.40; 'how': 0.40; 'ensure': 0.60; 'tell': 0.60; 'new': 0.61; 'show': 0.63; 'become': 0.64; 'more': 0.64; 'inline': 0.74; 'pasting': 0.84; 'received:125': 0.84; 'standing': 0.84; 'giants': 0.91; 'response,': 0.91; 'quotation': 0.93; 'scott': 0.93 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: Ben Finney Subject: Re: Python 2.7.6 help with white spaces? Date: Fri, 07 Feb 2014 16:24:34 +1100 References: <504A0CAE-42E4-495E-96AA-C8A45559E139@cox.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Gmane-NNTP-Posting-Host: vmx15867.hosting24.com.au X-Public-Key-ID: 0xBD41714B X-Public-Key-Fingerprint: 9CFE 12B0 791A 4267 887F 520C B7AC 2E51 BD41 714B X-Public-Key-URL: http://www.benfinney.id.au/contact/bfinney-gpg.asc X-Post-From: Ben Finney User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux) Cancel-Lock: sha1:EgK/XtHwCu47O0BVOmQ5ZLlIars= 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: 32 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1391750685 news.xs4all.nl 2888 [2001:888:2000:d::a6]:56703 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:65596 Scott W Dunning writes: > I keep trying differnt things but, I’m just very new to this. A few things that will make your communications more fruitful: * Please don't top-post. Trim the quoted material to the parts relevant for your response, and respond inline like a normal discussion. * Ensure that your message composer doesn't munge your text. The code you show us needs to be *exactly* what the Python interpreter will see; turn off anything which replaces one character with another (such as quotation marks), or wraps the code lines. * When asking about an error, *show us* the error by pasting exactly what the error is, including the part where it shows what line raised the exception. * Tell us what you expected the code to do, and how its behaviour is violating your expectations. Thanks for joining discussions here, hopefully you can become a good part of this community. -- \ “If I haven't seen as far as others, it is because giants were | `\ standing on my shoulders.” —Hal Abelson | _o__) | Ben Finney