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, ezio.melotti, ingo.janssen
Date 2010-11-15.15:24:32
SpamBayes Score 1.759714e-05
Marked as misclassified No
Message-id <1289834674.31.0.433282212685.issue10427@psf.upfronthosting.co.za>
In-reply-to
Content
+1

Note that in Python, semi-open intervals are favored, but specifying the last hour of the day is awkward when using datetime (as OP mentioned) and impossible using just time.  Using closed intervals is not a good work-around in many cases because it requires the user to be explicit about precision:  is the last hour [23:00-23:59], [23:00:00-23:59:00], or [23:00:00.999999-23:59:00.999999]?

I offer to write the patch for the C implementation if someone comes up with a patch for datetime.py including tests.
History
Date User Action Args
2010-11-15 15:24:34belopolskysetrecipients: + belopolsky, ezio.melotti, ingo.janssen
2010-11-15 15:24:34belopolskysetmessageid: <1289834674.31.0.433282212685.issue10427@psf.upfronthosting.co.za>
2010-11-15 15:24:32belopolskylinkissue10427 messages
2010-11-15 15:24:32belopolskycreate