Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On Sun, Sep 5, 2021 at 12:39 PM Alan Gauld via Python-list wrote: > > On 03/09/2021 18:37, Chris Angelico wrote: > > Without DST the schools opened in the dark so all the kids > had to travel to school in the dark and the number of > traffic accidents while crossing roads jumped. >

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On 03/09/2021 18:37, Chris Angelico wrote: Without DST the schools opened in the dark so all the kids had to travel to school in the dark and the number of traffic accidents while crossing roads jumped. > > Are you saying that you had DST in winter, or that, when summer *and* > DST

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On 2021-09-04 21:48:14 +0200, Peter J. Holzer wrote: > On 2021-09-02 08:32:36 +0100, Alan Gauld via Python-list wrote: > > On 31/08/2021 22:32, Chris Angelico wrote: > > > If we could abolish DST world-wide, life would be far easier. All the > > > rest of it would be easy enough to handle. > > We t

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On 2021-09-02 08:32:36 +0100, Alan Gauld via Python-list wrote: > On 31/08/2021 22:32, Chris Angelico wrote: > > If we could abolish DST world-wide, life would be far easier. All the > > rest of it would be easy enough to handle. > We tried that in the UK for 2 years back in the '70s and very > qui

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On Sat, Sep 4, 2021 at 3:33 AM Alan Gauld via Python-list wrote: > > On 02/09/2021 19:30, Chris Angelico wrote: > > >> Without DST the schools opened in the dark so all the kids > >> had to travel to school in the dark and the number of > >> traffic accidents while crossing roads jumped. > > > > H

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On 02/09/2021 19:30, Chris Angelico wrote: >> Without DST the schools opened in the dark so all the kids >> had to travel to school in the dark and the number of >> traffic accidents while crossing roads jumped. > > How do they manage in winter? That was the winter. Sunrise wasn't till 10:00 or

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On Fri, Sep 3, 2021 at 8:01 AM Alan Gauld via Python-list wrote: > > On 02/09/2021 19:28, Chris Angelico wrote: > > >> Except for the places that don't follow the IANA scheme and/or > >> dynamically change their time settings on a whim. To be complete > >> you need the ability to manually override

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On 02/09/2021 20:11, MRAB wrote: >> In one of them (I can't recall which is which) they change on the 4th >> weekend of October/March in the other they change on the last weekend. >> >> > In the EU (and UK) it's the last Sunday in March/October. > > In the US it's second Sunday in March and the f

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On Fri, Sep 3, 2021 at 4:40 AM Alan Gauld via Python-list wrote: > > On 31/08/2021 23:31, Chris Angelico wrote: > > > Ah, good to know. I think that actually makes a lot of sense; in the > > US, they try to let everyone pretend that the rest of the world > > doesn't exist ("we always change at 2AM

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On 02/09/2021 19:28, Chris Angelico wrote: >> Except for the places that don't follow the IANA scheme and/or >> dynamically change their time settings on a whim. To be complete >> you need the ability to manually override too. >> > > What places are those? Mainly small non-tech oriented places

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On Fri, Sep 3, 2021 at 4:26 AM Alan Gauld via Python-list wrote: > > On 31/08/2021 22:32, Chris Angelico wrote: > > > If we could abolish DST world-wide, life would be far easier. All the > > rest of it would be easy enough to handle. > We tried that in the UK for 2 years back in the '70s and very

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On 2021-09-02 08:40, Alan Gauld via Python-list wrote: On 31/08/2021 23:31, Chris Angelico wrote: Ah, good to know. I think that actually makes a lot of sense; in the US, they try to let everyone pretend that the rest of the world doesn't exist ("we always change at 2AM"), but in Europe, they t

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On Fri, Sep 3, 2021 at 4:22 AM Alan Gauld via Python-list wrote: > > On 31/08/2021 22:13, Chris Angelico wrote: > > > But ultimately, it all just means that timezones are too hard for > > humans to handle, and we MUST handle them using IANA's database. It is > > the only way. > > Except for the pl

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On Fri, Sep 3, 2021 at 4:18 AM Dennis Lee Bieber wrote: > > On Tue, 31 Aug 2021 16:53:14 -0500, 2qdxy4rzwzuui...@potatochowder.com > declaimed the following: > > >On 2021-09-01 at 07:32:43 +1000, > >Chris Angelico wrote: > >> If we could abolish DST world-wide, life would be far easier. All the >

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On 31/08/2021 23:31, Chris Angelico wrote: > Ah, good to know. I think that actually makes a lot of sense; in the > US, they try to let everyone pretend that the rest of the world > doesn't exist ("we always change at 2AM"), but in Europe, they try to > synchronize for the convenience of commerce

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On 31/08/2021 22:32, Chris Angelico wrote: > If we could abolish DST world-wide, life would be far easier. All the > rest of it would be easy enough to handle. We tried that in the UK for 2 years back in the '70s and very quickly reverted to DST when they realized that the number of fatalities amo

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On 31/08/2021 22:13, Chris Angelico wrote: > But ultimately, it all just means that timezones are too hard for > humans to handle, and we MUST handle them using IANA's database. It is > the only way. Except for the places that don't follow the IANA scheme and/or dynamically change their time sett

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On Tue, 31 Aug 2021 16:53:14 -0500, 2qdxy4rzwzuui...@potatochowder.com declaimed the following: >On 2021-09-01 at 07:32:43 +1000, >Chris Angelico wrote: >> If we could abolish DST world-wide, life would be far easier. All the >> rest of it would be easy enough to handle. > >Agreed. > Unf

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On Wed, 1 Sep 2021 09:38:30 +1000, Chris Angelico declaimed the following: >Yeah, I have no idea where the "farmers" explanation came from. >Growing up, we had some friends in countrified areas, including a >sheep farmer who showed us a ton of stuff about how shearing worked, >how moronic sheep

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On Wed, 1 Sep 2021 11:19:03 +1200, dn via Python-list declaimed the following: >time-zones. (Yes, you did say "CA", but easily 'missed' - by author and >reader alike) Or possibly misread as the Peoples Republic of CALIFORNIA (even if there isn't a "New Brunswick" in the PRCa)

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On 31/08/2021 16.13, Chris Angelico wrote: But ultimately, it all just means that timezones are too hard for humans to handle, and we MUST handle them using IANA's database. It is the only way. Tom Scott makes this point quite strongly on Computerphile:

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On 01/09/2021 11.27, MRAB wrote: > On 2021-08-31 23:31, Chris Angelico wrote: >> On Wed, Sep 1, 2021 at 8:22 AM MRAB wrote: >>> >>> [snip] >>> In the EU, DST in the member states changes at the same time. It's not >>> like the US where it ripples across the timezones, so the differences >>> vary d

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

> Yeah. And if you think you've heard it all, sign up for the > tzdata-announce mailing list and wait for the next phenomenon. I think > Egypt (Africa/Cairo) is currently in the lead for weirdest timezone > change, for (with short notice) announcing that they'd have DST during > summer but not duri

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On Wed, Sep 1, 2021 at 9:20 AM dn via Python-list wrote: > > On 01/09/2021 09.13, Chris Angelico wrote: > > On Wed, Sep 1, 2021 at 6:38 AM dn via Python-list > > wrote: > >>> Yeah. I do recommend making good use of the IANA tzinfo database > >>> though (especially since Python 3.9 made that a bit

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On 2021-08-31 23:31, Chris Angelico wrote: On Wed, Sep 1, 2021 at 8:22 AM MRAB wrote: [snip] In the EU, DST in the member states changes at the same time. It's not like the US where it ripples across the timezones, so the differences vary during the change. It all happens in one go. Ah, goo

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On 01/09/2021 09.13, Chris Angelico wrote: > On Wed, Sep 1, 2021 at 6:38 AM dn via Python-list > wrote: >>> Yeah. I do recommend making good use of the IANA tzinfo database >>> though (especially since Python 3.9 made that a bit easier to access), >>> as it's usually easier to get people to tell y

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On Wed, Sep 1, 2021 at 8:22 AM MRAB wrote: > > [snip] > In the EU, DST in the member states changes at the same time. It's not > like the US where it ripples across the timezones, so the differences > vary during the change. It all happens in one go. > Ah, good to know. I think that actually make

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On 2021-08-31 22:53, 2qdxy4rzwzuui...@potatochowder.com wrote: On 2021-09-01 at 07:32:43 +1000, Chris Angelico wrote: On Wed, Sep 1, 2021 at 7:17 AM <2qdxy4rzwzuui...@potatochowder.com> wrote: > What about Phoenix? In the winter, it's the same time there as it is in > San Francisco, but in

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On Wed, Sep 1, 2021 at 7:54 AM <2qdxy4rzwzuui...@potatochowder.com> wrote: > > On 2021-09-01 at 07:32:43 +1000, > Chris Angelico wrote: > > > On Wed, Sep 1, 2021 at 7:17 AM <2qdxy4rzwzuui...@potatochowder.com> wrote: > > > > What about Phoenix? In the winter, it's the same time there as it is in

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On 2021-09-01 at 07:32:43 +1000, Chris Angelico wrote: > On Wed, Sep 1, 2021 at 7:17 AM <2qdxy4rzwzuui...@potatochowder.com> wrote: > > What about Phoenix? In the winter, it's the same time there as it is in > > San Francisco, but in the summer, it's the same time there as it is in > > Denver (

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On Wed, Sep 1, 2021 at 7:17 AM <2qdxy4rzwzuui...@potatochowder.com> wrote: > > On 2021-09-01 at 08:36:55 +1200, > dn via Python-list wrote: > > > ... there is less consideration about working-out what time it is in > > Pune cf Kolkata, than between (say) San Francisco and Denver - > > although the

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On 2021-09-01 at 08:36:55 +1200, dn via Python-list wrote: > ... there is less consideration about working-out what time it is in > Pune cf Kolkata, than between (say) San Francisco and Denver - > although they are in the same country, are they in the same time-zone, > or not? (they aren't!) Wh

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On Wed, Sep 1, 2021 at 6:38 AM dn via Python-list wrote: > > Yeah. I do recommend making good use of the IANA tzinfo database > > though (especially since Python 3.9 made that a bit easier to access), > > as it's usually easier to get people to tell you what city/state > > they're in, rather than

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On 01/09/2021 00.45, Chris Angelico wrote: > On Tue, Aug 31, 2021 at 8:55 PM MRAB wrote: >> On 2021-08-31 02:16, dn via Python-list wrote: >>> On 31/08/2021 11.07, Dennis Lee Bieber wrote: On Sun, 29 Aug 2021 19:49:19 -0700 (PDT), "hongy...@gmail.com" declaimed the following: >>> ... >>

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On 31/08/2021 13:45, Chris Angelico wrote: > (I find the Ireland situation particularly amusing. Time zones and daylight saving arrangements in particular are a nightmare at the micro level. I once worked on a large customer support application which required all dates/times to be viewable in UT

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On Tuesday, August 31, 2021 at 7:55:51 AM UTC+8, Dennis Lee Bieber wrote: > On Sun, 29 Aug 2021 19:49:19 -0700 (PDT), "hongy...@gmail.com" > declaimed the following: > >On Ubuntu 20.04.2 LTS, I use the > >[recent2](https://github.com/dotslash/recent2/blob/master/recent2.py) to log > >and query

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On Tue, Aug 31, 2021 at 8:55 PM MRAB wrote: > > On 2021-08-31 02:16, dn via Python-list wrote: > > On 31/08/2021 11.07, Dennis Lee Bieber wrote: > >> On Sun, 29 Aug 2021 19:49:19 -0700 (PDT), "hongy...@gmail.com" > >> declaimed the following: > > ... > > > >> Might have helped to mention you

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On 2021-08-31 02:16, dn via Python-list wrote: On 31/08/2021 11.07, Dennis Lee Bieber wrote: On Sun, 29 Aug 2021 19:49:19 -0700 (PDT), "hongy...@gmail.com" declaimed the following: ... Might have helped to mention you were in China... To me, CST is North America Central Standard Time

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On 31/08/2021 11.07, Dennis Lee Bieber wrote: > On Sun, 29 Aug 2021 19:49:19 -0700 (PDT), "hongy...@gmail.com" > declaimed the following: ... > Might have helped to mention you were in China... To me, CST is North > America Central Standard Time (and I'd have expected this time of year to >

Re: The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On Sun, 29 Aug 2021 19:49:19 -0700 (PDT), "hongy...@gmail.com" declaimed the following: >On Ubuntu 20.04.2 LTS, I use the >[recent2](https://github.com/dotslash/recent2/blob/master/recent2.py) to log >and query my bash history, which uses a sqlite3 database to store the history >information. T

The sqlite3 timestamp conversion between unixepoch and localtime can't be done according to the timezone setting on the machine automatically.

On Ubuntu 20.04.2 LTS, I use the [recent2](https://github.com/dotslash/recent2/blob/master/recent2.py) to log and query my bash history, which uses a sqlite3 database to store the history information. The `datetime` of running a command is inserted in the sqlite3 database with [a `unixepoch` f