This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author loewis
Recipients Arfrever, amaury.forgeotdarc, denilsonsa, giampaolo.rodola, loewis, neologix, pitrou, rosslagerwall, zbysz
Date 2012-01-05.20:54:59
SpamBayes Score 8.069203e-06
Marked as misclassified No
Message-id <>
I haven't read much of this issue, but I strongly dislike the use of named tuples. Either we want people to use named fields, then we should use a regular class (possibly with slots), or we want to define the result as two values, then there should be a plain tuple result.

named tuples should only be used as a compatibility mechanism, when the first design used tuples, and it was later found that additional values need to be returned which would change the number of values (or the original design was considered bad because it returned too many positional values to properly keep track).
Date User Action Args
2012-01-05 20:55:00loewissetrecipients: + loewis, amaury.forgeotdarc, pitrou, giampaolo.rodola, Arfrever, zbysz, denilsonsa, neologix, rosslagerwall
2012-01-05 20:55:00loewissetmessageid: <>
2012-01-05 20:54:59loewislinkissue13609 messages
2012-01-05 20:54:59loewiscreate