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 nevgor
Recipients facundobatista, nevgor
Date 2008-07-03.14:03:56
SpamBayes Score 0.009092378
Marked as misclassified No
Message-id <8acd28da0807030703o17542943rb36968ff646fab2e@mail.gmail.com>
In-reply-to <1215092961.52.0.978720618937.issue3269@psf.upfronthosting.co.za>
Content
- 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 is confusing!
- I just wanted to point out that Python should be consistent: to provide
the same behaviour for 60,61 and 62 sec.

The conclusion is over as far as I am concerned.
I got the picture (you standpoint), and I hope, you too.

Thank you, once again,

Regards

     Neven

----------------------

On Thu, Jul 3, 2008 at 3:49 PM, Facundo Batista <report@bugs.python.org>
wrote:

>
> Facundo Batista <facundo@taniquetil.com.ar> 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 date?
>
> I suggest to bring this issue in the python list if you have further
> doubts.
>
> Thank you!!
>
> ----------
> resolution:  -> invalid
> status: open -> closed
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue3269>
> _______________________________________
>
Files
File name Uploaded
unnamed nevgor, 2008-07-03.14:03:54
History
Date User Action Args
2008-07-03 14:03:58nevgorsetspambayes_score: 0.00909238 -> 0.009092378
recipients: + nevgor, facundobatista
2008-07-03 14:03:56nevgorlinkissue3269 messages
2008-07-03 14:03:56nevgorcreate