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 belopolsky
Recipients belopolsky, techtonik
Date 2010-06-08.17:59:02
SpamBayes Score 0.0025474099
Marked as misclassified No
Message-id <1276019944.53.0.915496597645.issue8902@psf.upfronthosting.co.za>
In-reply-to
Content
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() may lead so people to call date.today() and time.now() separately instead of datetime.now() leading to interesting bugs.

One think I would consider an improvement over the current situation, would be to rename date.today() to date.now().  There are too many ways to spell the same thing:

date.today()
datetime.today()
datetime.now().date()

and no easy way to write a "how long ago" function that would work for both date and datetime:

def ago(t):
    t.now() - t
History
Date User Action Args
2010-06-08 17:59:04belopolskysetrecipients: + belopolsky, techtonik
2010-06-08 17:59:04belopolskysetmessageid: <1276019944.53.0.915496597645.issue8902@psf.upfronthosting.co.za>
2010-06-08 17:59:02belopolskylinkissue8902 messages
2010-06-08 17:59:02belopolskycreate