Hi Ken,
----- Original Message -----
> On 22/03/16 08:17, Ken McDonell wrote:
> [...]
> inseconds = 0.0
> try:
> inseconds = time.mktime(timetuple)
> except:
> pass
> return "%s %s" % (inseconds.__str__(), timetuple)
>
> I don't see the point of this ... inseconds can _never_ be anything
> useful, as it will be constructed using the _local_ timezone, not the
> PMAPI TimeZone. And indeed this number is the value above for all hosts
> in Melbourne, but something quite different for grundy.sgi.com in the USA.
Yep, not sure why its not using __pmMktime(3) ... looking again, I suspect
that was the intent rather than the python time call there.
> Why don't we skip all the inseconds stuff and simply
>
> return str(timetuple)
That would give a string like "(2003, 02, 3, ...)" and not a timestamp in
the mktime form we were after I guess.
> > and why is str(..) needed in the first case, but not the second?
>
> and I still have no clue on this.
>
Not sure either, I'll dig deeper on both fronts tomorrow.
cheers.
--
Nathan
|