[issue8902] add datetime.time.now() for consistency

Changes by Berker Peksag : -- stage: needs patch -> resolved ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue8902] add datetime.time.now() for consistency

Raymond Hettinger added the comment: For the reasons listed by others, marking this as closed/rejected. -- nosy: +rhettinger resolution: -> rejected status: open -> closed ___ Python tracker ___

[issue8902] add datetime.time.now() for consistency

Alexander Belopolsky added the comment: I would like to bring this issue to some conclusion. Here is the summary: Pro: datetime.time.now() is shorter than datetime.datetime.now().time() Cons: 1. date, time = datetime.date.today(), datetime.time.now() is attractive, but wrong. 2. tim

[issue8902] add datetime.time.now() for consistency

Changes by R. David Murray : -- nosy: +r.david.murray ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue8902] add datetime.time.now() for consistency

Changes by Ezio Melotti : -- nosy: +ezio.melotti versions: +Python 3.4 -Python 3.3 ___ Python tracker ___ ___ Python-bugs-list mailing

[issue8902] add datetime.time.now() for consistency

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

[issue8902] add datetime.time.now() for consistency

Changes by Alexander Belopolsky : -- resolution: wont fix -> status: closed -> open ___ Python tracker ___ ___ Python-bugs-list mailin

[issue8902] add datetime.time.now() for consistency

anatoly techtonik added the comment: And I certainly don't agree with you that usability changes in API are not use cases. -- ___ Python tracker ___

[issue8902] add datetime.time.now() for consistency

anatoly techtonik added the comment: I'd say no consensus was reached due to lack of participation. My enthusiasm was killed by the issue8903 resolution. My opinion is that: datetime.time.now() is much better than: datetime.datetime.now().time() -- _

[issue8902] add datetime.time.now() for consistency

Alexander Belopolsky added the comment: Closing for the lack of interest. Proposed time.now() is already available as datetime.now().time(). No use case justifying any improvement in this area was presented. -- resolution: postponed -> wont fix status: open -> closed __

[issue8902] add datetime.time.now() for consistency

Changes by Alexander Belopolsky : -- resolution: -> postponed versions: +Python 3.3 -Python 3.2 ___ Python tracker ___ ___ Python-bugs

[issue8902] add datetime.time.now() for consistency

Changes by Alexander Belopolsky : -- stage: -> needs patch type: -> feature request versions: -Python 2.7, Python 3.1, Python 3.3 ___ Python tracker ___ ___

[issue8902] add datetime.time.now() for consistency

Alexander Belopolsky added the comment: I need to correct myself: datetime.today() is not an alternative spelling of date.today(), but rather a function returning current datetime which subtly different from datetime.now(). -- ___ Python tracker <

[issue8902] add datetime.time.now() for consistency

Alexander Belopolsky added the comment: Anatoly, msg107191 belongs to issue8903, not here and it is not a use case, but rather a demonstration of how the proposed feature would work. My question is why would an application need current time without current date? I feel providing time.now()

[issue8902] add datetime.time.now() for consistency

anatoly techtonik added the comment: > Didn't you just recently complain about the large number of functions in > datetime module? About verbosity of datetime API to be exact, so it is a ratio of (API functions + required docs)/user code that makes required stuff done. -- __

[issue8902] add datetime.time.now() for consistency

anatoly techtonik added the comment: > What is your use case? >>> from datetime import now, today >>> now() datetime.time ... >>> today() datetime.date ... -- ___ Python tracker ___

[issue8902] add datetime.time.now() for consistency

Alexander Belopolsky added the comment: Anatoly, Didn't you just recently complain about the large number of functions in datetime module? (issue7584) datetime.datetime.now().time() seems adequate to me. What is your use case? -- assignee: -> belopolsky nosy: +belopolsky priority:

[issue8902] add datetime.time.now() for consistency

New submission from anatoly techtonik : There is: datetime.date.today() datetime.datetime.today() datetime.datetime.now([tz]) But no: datetime.time.now([tz]) -- components: Library (Lib) messages: 107122 nosy: techtonik priority: normal severity: normal status: open title: add datetime.