Message81172
| Author | rhettinger |
|---|---|
| Recipients | brett.cannon, christian.heimes, eric.smith, exarkun, loewis, ncoghlan, rhettinger, ross.light |
| Date | 2009-02-04.22:33:50 |
| SpamBayes Score | 5.871452e-05 |
| Marked as misclassified | No |
| Message-id | <1233786831.81.0.770356348674.issue4285@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> Eric Smith <eric@trueblade.com> added the comment: > "... as a named tuple" works for me. I'll go with that. Thanks! +1 Remember, "named tuple" is a concept, not a class. It is anything that provides attribute access as an alternative to indexed access (see the definition in the glossary where time.struct_time is given as an example). Running the collections.named_tuple() factory function creates a new class with named tuple features, but it is just one of several ways of creating named tuples. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2009-02-04 22:33:51 | rhettinger | set | recipients: + rhettinger, loewis, brett.cannon, exarkun, ncoghlan, eric.smith, christian.heimes, ross.light |
| 2009-02-04 22:33:51 | rhettinger | set | messageid: <1233786831.81.0.770356348674.issue4285@psf.upfronthosting.co.za> |
| 2009-02-04 22:33:50 | rhettinger | link | issue4285 messages |
| 2009-02-04 22:33:50 | rhettinger | create | |