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 pitrou
Recipients belopolsky, jborgohain, lemburg, mark.dickinson, mwtoews, pitrou
Date 2010-05-20.23:27:16
SpamBayes Score 0.06585394
Marked as misclassified No
Message-id <1274398033.3141.5.camel@localhost.localdomain>
In-reply-to <1274397467.31.0.643844939306.issue1436346@psf.upfronthosting.co.za>
Content
> I think this should be rejected.  The OP's premise was that
> t.timetuple()[7] was unreadable, but in the modern python, the same
> can be written as t.timetuple().tm_yday.

Could I suggest such example be added to the documentation, though?
The datetime / time jungle is difficult to navigate through, and I think
for most people it is not obvious that the answer to their needs is to
look at one of the attributes of the timetuple() result...
History
Date User Action Args
2010-05-20 23:27:17pitrousetrecipients: + pitrou, lemburg, mark.dickinson, belopolsky, mwtoews, jborgohain
2010-05-20 23:27:16pitroulinkissue1436346 messages
2010-05-20 23:27:16pitroucreate