Re: time.strftime in 2.4.1 claims data out of range when not

2005-04-22 Thread Tim Peters
[Sheila King] > I have a web app that has been running just fine for several months under > Python 2.2.2. > > We are preparing to upgrade the server to run Python 2.4.1. > > However, part of my web app is throwing an error on this code (that has > previously worked without exception): > > >>> time.

Re: time.strftime in 2.4.1 claims data out of range when not

2005-04-22 Thread Kent Johnson
Raymond Hettinger wrote: Since the rules for handling missing, inconsistent, or out-of-range tuple fields are not defined, even that revision has some risk. To future-proof the code, use strptime() to generate a well-formed time tuple: strptime('%d-%d-%d' % (y,m,d), '%Y-%m-%d') (2005, 5, 15, 0, 0,

Re: time.strftime in 2.4.1 claims data out of range when not

2005-04-22 Thread Raymond Hettinger
[Sheila King] > I have a web app that has been running just fine for several months under > Python 2.2.2. > > We are preparing to upgrade the server to run Python 2.4.1. > > However, part of my web app is throwing an error on this code (that has > previously worked without exception): > > >>> time.

Re: time.strftime in 2.4.1 claims data out of range when not

2005-04-22 Thread Brian van den Broek
Sheila King said unto the world upon 2005-04-22 02:45: I have a web app that has been running just fine for several months under Python 2.2.2. We are preparing to upgrade the server to run Python 2.4.1. However, part of my web app is throwing an error on this code (that has previously worked wit

time.strftime in 2.4.1 claims data out of range when not

2005-04-21 Thread Sheila King
I have a web app that has been running just fine for several months under Python 2.2.2. We are preparing to upgrade the server to run Python 2.4.1. However, part of my web app is throwing an error on this code (that has previously worked without exception): >>> time.strftime("%Y-%m-%d", (Y, M,