[issue8903] Add module level now() and today() functions to datetime module

anatoly techtonik added the comment: Raymond mention your reasons please. I may need them one day for describing development process. -- ___ Python tracker ___ _

[issue8903] Add module level now() and today() functions to datetime module

Changes by Raymond Hettinger : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue8903] Add module level now() and today() functions to datetime module

Raymond Hettinger added the comment: FWIW, I concur with the rejection. -- nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-li

[issue8903] Add module level now() and today() functions to datetime module

Alexander Belopolsky added the comment: On Thu, Jun 10, 2010 at 10:37 PM, R. David Murray wrote: > > R. David Murray added the comment: > > I actually agree with Anatoly here.  I find it much more intuitive to do > >  import datetime > >   timestamp = datetime.now() > > than to do > >   timest

[issue8903] Add module level now() and today() functions to datetime module

R. David Murray added the comment: I actually agree with Anatoly here. I find it much more intuitive to do import datetime timestamp = datetime.now() than to do timestamp = datetime.datetime.now() I always have to remember that 'now' is a class method, often after getting a "date

[issue8903] Add module level now() and today() functions to datetime module

Alexander Belopolsky added the comment: Note that it is important to keep class methods because in some cases it is convenient to obtain now/today from datetime/date instances instead of importing them from the module. So deprecating class methods is not an option and adding module level fun