Neven Goršić <[EMAIL PROTECTED]> added the comment:
- My original issue was that time.strptime() makes difference between 61 and
62 seconds
- 17h AM, 78 s, 128min everyone can easly transform correctly, I just wanted
to use function for
boundarie checking: rising error for 62 sec and not for 61
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Closing as invalid, two reasons:
- Your original issue was that time.strptime() didn't allow 62 seconds,
not that it allowed 60 or 61.
- If you use it to validate input... how do you actually know that
03/25/2012 17:13:61 AM' is an invalid
Neven Goršić <[EMAIL PROTECTED]> added the comment:
Thank you for your reply, although is not helpful for me.
I use strptime() for datedate transformation and datatime boundaries
checking
and therefore I am not conserned in Reltivity theory.
When someone in datetime table enter 02:61:38 it is s
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Minutes with 61 (0..60) and 62 (0..61) seconds are used to adjust the
theoretical calendar because of small differences with real world
rotation...
Are you aware of any case where a minute with 63 seconds (0..62) should
be used?
--
New submission from Neven Goršić <[EMAIL PROTECTED]>:
strptime() allows 60 and 61 sec, but not 62 sec in arg. string
>>> s='02/28/2000 12:33:61 AM'
>>> time.strptime(s,'%m/%d/%Y %I:%M:%S %p')
(2000, 2, 28, 0, 33, 61, 0, 59, -1)
>>> s='02/28/2000 12:33:62 AM'
>>> time.strptime(s,'%m/%d/%Y %I:%M
