Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!npeer.de.kpn-eurorings.net!npeer-ng0.de.kpn-eurorings.net!xlned.com!feeder5.xlned.com!newsfeed.xs4all.nl!newsfeed1.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.022 X-Spam-Evidence: '*H*': 0.96; '*S*': 0.00; 'constructor': 0.07; 'immutable': 0.09; 'instances.': 0.09; 'tuple': 0.09; 'cc:addr :python-list': 0.10; '(rather': 0.16; 'benjamin': 0.16; 'cc:name:python list': 0.16; 'hashable': 0.16; 'immutable,': 0.16; 'mechanism.': 0.16; 'namedtuple': 0.16; 'namedtuples': 0.16; "type's": 0.16; 'wrote:': 0.17; '>>>': 0.18; 'supposed': 0.21; 'tuples': 0.22; 'cc:2**0': 0.23; 'example': 0.23; 'seems': 0.23; 'cc:addr:python.org': 0.25; 'header:In-Reply-To:1': 0.25; 'header :User-Agent:1': 0.26; 'wonder': 0.27; 'restrict': 0.27; 'interface': 0.27; '>>>>': 0.29; 'relies': 0.29; 'though.': 0.29; 'objects': 0.29; 'expect': 0.31; 'could': 0.32; 'doubt': 0.33; 'instances': 0.33; 'values.': 0.33; 'hi,': 0.33; "can't": 0.34; 'there': 0.35; 'really': 0.36; 'message-id:@gmail.com': 0.36; 'itself': 0.37; 'why': 0.37; 'subject:: ': 0.38; 'object': 0.38; 'things': 0.38; 'little': 0.39; 'john': 0.60; 'places': 0.61; 'provide': 0.62; 'different': 0.63; 'received:ac.uk': 0.65; 'said:': 0.65; 'hoping': 0.72; '2013': 0.84; 'anywhere.': 0.84; 'oscar': 0.84; 'reid': 0.84; 'replacements': 0.84; 'factors': 0.95 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Date: Mon, 18 Feb 2013 14:18:49 +0000 From: John Reid User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Oscar Benjamin Subject: Re: Differences creating tuples and collections.namedtuples References: <7a40a426-baa9-46f8-8f9d-59ba32b044f3@googlegroups.com> <512231CA.8070108@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: "J.E. Reid" Cc: Python List 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: 29 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1361197131 news.xs4all.nl 6981 [2001:888:2000:d::a6]:47686 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:39094 On 18/02/13 14:12, Oscar Benjamin wrote: > On 18 February 2013 13:51, John Reid wrote: >> On 18/02/13 12:03, Oscar Benjamin wrote: >>> On 18 February 2013 11:47, John Reid wrote: >>>> Hi, >>>> >>>> I was hoping namedtuples could be used as replacements for tuples in all instances. >>> namedtuples are not really intended to serves as tuples anywhere. They >>> are intended to provide lightweight, immutable, hashable objects with >>> *named* (rather than numbered) values. >> If they are not supposed to be tuples then calling them namedtuples and >> inheriting from tuple seems a little odd. > You can use namedtuple instances in places that expect tuples. > Inheriting from tuples enables them to be all the things I said: > lightweight, immutable and hashable. The type object itself has a > different interface for the constructor, though. > > Then I can't use them in every place I use tuples. For example IPython relies upon the type's interface for the constructor as part of a serialization mechanism. I wonder why they have a different interface. It seems to restrict their usability. No doubt there were other factors involved in the design of the interface. John.