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, eric.araujo, ezio.melotti, ingo.janssen, mark.dickinson, rbp
Date 2010-11-21.20:55:39
SpamBayes Score 0.027060581
Marked as misclassified No
Message-id <AANLkTin0wbdz2W1GzZW_7aozqS-T=oBf=Nc-VuQ1N-vD@mail.gmail.com>
In-reply-to <1290372534.23.0.372628773275.issue10427@psf.upfronthosting.co.za>
Content
On Sun, Nov 21, 2010 at 3:48 PM, Mark Dickinson <report@bugs.python.org> wrote:
..
> Well, if all that's wanted is for hour==24 to be legal on input, with the datetime object
> itself being automatically normalized at creation time, then the choices seem simple: ..

What about time objects? If we take the "normalized at creation time"
approach, time(24) may still be disallowed.
History
Date User Action Args
2010-11-21 20:55:43belopolskysetrecipients: + belopolsky, mark.dickinson, rbp, ezio.melotti, eric.araujo, ingo.janssen
2010-11-21 20:55:39belopolskylinkissue10427 messages
2010-11-21 20:55:39belopolskycreate