[issue8907] time module documentation differs in trunk and py3k

Alexander Belopolsky added the comment: Merged r81489 to py3k (r81840), but this affects datetime module docs, not time. On a closer examination, the differences in time.rst are correct. -- resolution: -> invalid status: open -> closed ___ Python

[issue8907] time module documentation differs in trunk and py3k

Mark Dickinson added the comment: r81489 should probably also be svnmerged to py3k before applying this doc change. (As far as I can tell, this is the only outstanding unmerged trunk change.) -- nosy: +mark.dickinson ___ Python tracker

[issue8907] time module documentation differs in trunk and py3k

Alexander Belopolsky added the comment: .. also 3.x does not track versionadded from 2.x -- ___ Python tracker ___ ___ Python-bugs-lis

[issue8907] time module documentation differs in trunk and py3k

Alexander Belopolsky added the comment: There seems to be a few legitimate differences such as "int or long" vs. integer, or parenthesis for print. Patch is forthcoming. -- ___ Python tracker

[issue8907] time module documentation differs in trunk and py3k

Changes by Alexander Belopolsky : -- nosy: +d...@python ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue8907] time module documentation differs in trunk and py3k

New submission from Alexander Belopolsky : Doc/library/time.rst differs in trunk and py3k. It appears that the trunk version is more up to date and can simply replace the py3k version, but I would like to have another pair of eyes to take a look before committing. I also noticed that time.asc