Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!newsreader4.netcologne.de!news.netcologne.de!xlned.com!feeder7.xlned.com!newsfeed.xs4all.nl!newsfeed3.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.006 X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'subject:not': 0.03; 'attributes': 0.09; 'from:addr:ethan': 0.09; 'from:addr:stoneleaf.us': 0.09; 'from:name:ethan furman': 0.09; 'message-id:@stoneleaf.us': 0.09; 'subject:Why': 0.09; 'variant': 0.09; '~ethan~': 0.09; 'attributes,': 0.16; 'be:': 0.16; 'piotr': 0.16; 'received:69.93': 0.16; 'subject: \n ': 0.16; 'subject:accessing': 0.16; 'wrote:': 0.18; 'wed,': 0.18; 'code,': 0.22; 'print': 0.22; 'header:User-Agent:1': 0.23; 'right.': 0.26; 'pass': 0.26; 'header:In-Reply-To:1': 0.27; 'dec': 0.30; '(which': 0.31; 'too.': 0.31; 'class': 0.32; 'subject:with': 0.35; 'there': 0.35; 'charset:us-ascii': 0.36; 'subject:?': 0.36; 'should': 0.36; 'to:addr:python-list': 0.38; 'pm,': 0.38; 'to:addr:python.org': 0.39; 'skip:p 20': 0.39; 'received:173': 0.61; 'subject:there': 0.68; 'actually,': 0.84; 'subject:being': 0.84; 'yours': 0.88; 'received:gateway02.websitewelcome.com': 0.91; 'hill': 0.95; '2013': 0.98 Date: Wed, 04 Dec 2013 13:02:45 -0800 From: Ethan Furman User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: python-list@python.org Subject: Re: Why is there no natural syntax for accessing attributes with names not being valid identifiers? References: <15912943-29a1-4365-b027-7bb8cec447f8@googlegroups.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - gator3304.hostgator.com X-AntiAbuse: Original Domain - python.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - stoneleaf.us X-BWhitelist: no X-Source-IP: 173.12.184.233 X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: ([173.12.184.233]) [173.12.184.233]:41150 X-Source-Auth: ethan+stoneleaf.us X-Email-Count: 2 X-Source-Cap: dG9idWs7dG9idWs7Z2F0b3IzMzA0Lmhvc3RnYXRvci5jb20= 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: 26 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1386192424 news.xs4all.nl 2868 [2001:888:2000:d::a6]:58571 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:61051 On 12/04/2013 12:58 PM, Jerry Hill wrote: > On Wed, Dec 4, 2013 at 3:35 PM, Piotr Dobrogost > wrote: >> Right. If there's already a way to have attributes with these "non-standard" names (which is a good thing) then for uniformity with dot access to attributes with "standard" names there should be a variant of dot access allowing to access these "non-standard" named attributes, too. > > Given the follow code, what do you think should print? > > class My_Class(object): > pass > > bar = 1 > my_object = My_Class() > setattr(my_object, 'foo', 10) > setattr(my_object, 'bar', 100) > setattr(my_object, 'foo-bar', 1000) > > print(my_object.foo-bar) Actually, under his proposal it would be: print(my_object."foo-bar") and it would print 1000, while yours would still print 9. -- ~Ethan~