[issue1436346] yday in datetime module

Georg Brandl added the comment: Committed in r81489. Thanks! -- resolution: -> fixed status: open -> closed ___ Python tracker ___ __

[issue1436346] yday in datetime module

Changes by Alexander Belopolsky : -- assignee: belopolsky -> components: +Documentation keywords: +needs review versions: +Python 2.7 ___ Python tracker ___ __

[issue1436346] yday in datetime module

Alexander Belopolsky added the comment: Attaching a documentation patch. -- Added file: http://bugs.python.org/file17446/issue1436346-doc.diff ___ Python tracker ___ _

[issue1436346] yday in datetime module

Georg Brandl added the comment: Care to suggest a patch? -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue1436346] yday in datetime module

Changes by Alexander Belopolsky : -- nosy: +georg.brandl ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue1436346] yday in datetime module

Alexander Belopolsky added the comment: On Thu, May 20, 2010 at 7:27 PM, Antoine Pitrou wrote: > >> .. 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 do

[issue1436346] yday in datetime module

Antoine Pitrou added the comment: > 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 / tim

[issue1436346] yday in datetime module

Alexander Belopolsky added the comment: 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. The later is only slightly less readable than the proposed t.yday(). For the other

[issue1436346] yday in datetime module

Changes by Alexander Belopolsky : -- assignee: -> belopolsky ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue1436346] yday in datetime module

Changes by Antoine Pitrou : -- nosy: +belopolsky, mark.dickinson versions: -Python 2.7 ___ Python tracker ___ ___ Python-bugs-list

[issue1436346] yday in datetime module

Marc-Andre Lemburg added the comment: Hmm, looks like there's a bug in roundup's email interface... the code snippet should have read: >>> from mx.DateTime import * >>> today().day_of_year 217 >>> Date(2009, 1, 1) + (217 - 1) -- ___ Python tracker

[issue1436346] yday in datetime module

Marc-Andre Lemburg added the comment: Antoine Pitrou wrote: > > Antoine Pitrou added the comment: > > Some comments: > - since there is already a weekday() method, the new method should be > called yearday() rather than yday() > - ditto for fromyday(): fromyearday() would be better > - Module

[issue1436346] yday in datetime module

Antoine Pitrou added the comment: Some comments: - since there is already a weekday() method, the new method should be called yearday() rather than yday() - ditto for fromyday(): fromyearday() would be better - Modules/datetimemodule.c should only be indented with tabs, but your patch indents it

[issue1436346] yday in datetime module

Changes by Antoine Pitrou : -- nosy: +pitrou versions: +Python 3.2 -Python 3.1 ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue1436346] yday in datetime module

Jubaraj Borgohain added the comment: I have completed the following two new features for the datetime module (the changes are attached as a patch): a. Added a method yday() b. Added date.fromyday(year,yday), which returns a date object. The other features requested are already available. The tes

[issue1436346] yday in datetime module

Changes by Daniel Diniz : -- stage: -> test needed versions: +Python 2.7, Python 3.1 ___ Python tracker ___ ___ Python-bugs-list ma