TimeSpan

wxPython Users
1

I'm a bit of a novice my self, but here's my take: TimeSpan is, of course,
related to time but it does not point to a particular date or time. It is,
rather, the difference in time between two DateTimes, and carries inside
itself various expressions of that difference. For instance, in your case
you are getting the difference between two times separated by 120,000 years.
How many seconds is that? Pretty close to 120000 x 365.25 x 24 x 3600 =
3786912000000. Multiply this by 1000 and you get something very close to
your first value. But you're probably wondering about the negative values.
I would guess that your numbers are getting so large that they can't be
expressed in the memory available to an int. But like I said, I'm kind of a
novice myself. BTW, python proper has DateTime classes that work just as
well as the wx stuff. I would suggest you use those.

···

--
View this message in context: http://wxpython-users.1045709.n5.nabble.com/TimeSpan-tp5716915p5716939.html
Sent from the wxPython-users mailing list archive at Nabble.com.

2

bob sacamento wrote:

Multiply this by 1000 and you get something very close to
your first value. But you're probably wondering about the negative values.
I would guess that your numbers are getting so large that they can't be
expressed in the memory available to an int.

It's not stored in an int, it's stored in a 64-bit integer, and 64-bits
is more than enough for that value. You are half right, in that the
problem is some kind of overflow. However, after 15 minutes of looking
at the code, I don't fully understand where the overflow is occurring.
Given that this is the first time in 15 years that the problem has been
identified, and given that the problem doesn't occur in the wxPhoenix
code base, and given that the Python datetime class will work, it's not
really worth chasing any further.

···

--
Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.