Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!feeder.news-service.com!newsfeed.xs4all.nl!newsfeed5.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.000 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'expansion': 0.05; 'warnings': 0.05; 'builtins': 0.07; 'compiler': 0.07; 'subject:when': 0.07; 'python': 0.08; '(also': 0.09; '16,': 0.15; 'apply:': 0.16; 'bye,': 0.16; 'objection': 0.16; 'received:mindspring.com': 0.16; 'scope.': 0.16; 'subject:builtin': 0.16; 'warn': 0.16; 'x-mailer:apple mail (2.1084)': 0.16; 'looked': 0.16; 'wrote:': 0.16; 'language': 0.17; 'say,': 0.19; 'seems': 0.20; "haven't": 0.20; "doesn't": 0.22; 'header:In-Reply-To:1': 0.22; 'pm,': 0.24; 'aug': 0.24; 'library.': 0.24; "i'm": 0.27; 'compile': 0.29; 'asking': 0.29; 'context,': 0.30; 'subject:?': 0.31; 'changes': 0.31; 'received:24': 0.32; 'agree': 0.33; 'to:addr:python-list': 0.33; 'tools.': 0.34; 'running': 0.35; 'charset:us-ascii': 0.36; 'with.': 0.37; 'but': 0.37; 'steven': 0.38; 'should': 0.38; 'subject:: ': 0.39; 'header:Mime-Version:1': 0.39; 'to:addr:python.org': 0.39; 'header:Message-Id:1': 0.61; 'concerns': 0.80; 'received:69.73': 0.84 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1084) Subject: Re: Why no warnings when re-assigning builtin names? From: Philip Semanchuk In-Reply-To: <4e4b197b$0$29974$c3e8da3$5496439d@news.astraweb.com> Date: Tue, 16 Aug 2011 22:16:49 -0400 Content-Transfer-Encoding: quoted-printable References: <4e49c89a$0$30001$c3e8da3$5496439d@news.astraweb.com> <4e49fcd7$0$29974$c3e8da3$5496439d@news.astraweb.com> <2A3EB048-1F10-46E8-973F-9BBD303E7B9F@semanchuk.com> <4E4A8F94.50706@stoneleaf.us> <4E4A98AE.1070708@stoneleaf.us> <4e4b197b$0$29974$c3e8da3$5496439d@news.astraweb.com> To: python-list list X-Mailer: Apple Mail (2.1084) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - deimos.nocdirect.com X-AntiAbuse: Original Domain - python.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - semanchuk.com X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.12 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: 17 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1313547416 news.xs4all.nl 23843 [2001:888:2000:d::a6]:49583 X-Complaints-To: abuse@xs4all.nl Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:11650 On Aug 16, 2011, at 9:29 PM, Steven D'Aprano wrote: > I have no objection to lint tools. But separation of concerns should = apply: > the Python compiler should just compile what I tell it to, the linter > should warn me if I'm running with scissors. This point (also made by Ethan) I can agree with. I haven't looked = through all the warnings the Python compiler emits, but it seems like it = currently doesn't dispense advice (unlike, say, gcc). It only warns = about changes in the language & standard library. In that context, = asking it to warn about shadowing builtins would be an expansion of = scope.=20 bye, Philip=