e that comes to mind is python-dateutil,
> but I think there are others.
Thanks I will try it.
Once again, thanks for your helpfull responses !
Ivan
On Jun 9, 12:11 pm, Paul Boddie <[EMAIL PROTECTED]> wrote:
> On 9 Jun, 07:40, Ivan Velev <[EMAIL PROTECTED]> wrote:
>
>
>
Thanks Paul,
I have identified the "problem" - because of daylight change this
particular timesamp was observed twice in Europe/Sofia. Here is the
GMT-to-local-time conversion:
++-+-+
| gmt_stamp | gmt_time| local_time |
+
time is near the "daylight saving time change" moment)
On Jun 3, 6:01 pm, Paul Boddie <[EMAIL PROTECTED]> wrote:
> On 3 Jun, 16:12, Ivan Velev <[EMAIL PROTECTED]> wrote:
>
>
>
> > Minimal example below - it gives me different output if I comment /
> >
Hello,
Minimal example below - it gives me different output if I comment /
uncomment the extra time.mktime call - note that this call is not
related in any way to main logic flow.
When "problematicStamp = ..." is commented I get
gmtStamp: 1130634600.0
when I uncomment that line I get
gmtStamp:
