[20:32] <balloons> barry you wouldn't happen to be about would you?
[20:32] <barry> balloons: i am
[20:32] <balloons> so, I played with the overflow error a bit more
[20:32] <balloons> indeed, it's a 32bit issue I believe as you suggested
[20:33] <balloons> the self in question is 2980540800, greater than 238, etc
[20:35] <barry> balloons: i had to go through all manner of craziness to get systemimage to work on 32 bit: http://bazaar.launchpad.net/~ubuntu-system-image/ubuntu-system-image/client/view/head:/systemimage/image.py#L34
[20:35] <barry> (though that probably doesn't help you)
[20:35] <balloons> I suppose that begs the question why I'm trying to convert such high years.. and indeed I'm no
[20:35] <balloons> barry, I got it working using timedelta
[20:35] <balloons> autopilot should probably be tweaked.. it's where I tweaked the code
[20:36] <barry> yeah, 2064 ;)
[20:36] <balloons> apparently if you use a more pythonic datetime function, you get support for huge durations, while the native modules don't have it and are limited
[20:37] <barry> balloons: it's probably a platform limitation, i.e. python passing that value to some libc function and getting an error from that
[20:38] <balloons> barry, yep blame c :-)
[20:38] <barry> :)
[20:42] <balloons> anyways, thanks for the help.. though I still have to figure out a workaround for now :-)