On Wed, Mar 2, 2022 at 6:20 PM Peter J. Holzer wrote:
> On 2022-02-28 23:28:23 +0100, Morten W. Petersen wrote:
> > Well, let's say I specify the datetime 2022-02-22 02:02 (AM). I think
> > everyone could agree that it also means 2022-02-22 02:02:00:00, to
> > 2022-02-22 02:02:59:59.
>
> I disagr
On 2022-02-28 23:28:23 +0100, Morten W. Petersen wrote:
> Well, let's say I specify the datetime 2022-02-22 02:02 (AM). I think
> everyone could agree that it also means 2022-02-22 02:02:00:00, to
> 2022-02-22 02:02:59:59.
I disagree. The datetime 2022-02-22 02:02 specifies a point in time, not
a
On Tue, 1 Mar 2022 at 22:52, Morten W. Petersen wrote:
> Yep. Well, as I said, I could create some range objects myself, and even
> create a little module and put it up on pypi, if I couldn't find any existing
> module I could use.
>
> As we're discussing this, it is clear that different point
Forwarding to the list..
-- Forwarded message -
From: Morten W. Petersen
Date: Tue, Mar 1, 2022 at 12:52 PM
Subject: Re: Timezone for datetime.date objects
To: Chris Angelico
On Mon, Feb 28, 2022 at 11:57 PM Chris Angelico wrote:
> On Tue, 1 Mar 2022 at 09:28, Morte
On Tue, 1 Mar 2022 at 09:28, Morten W. Petersen wrote:
>
> Hi Chris, Cameron.
>
> Well, let's say I specify the datetime 2022-02-22 02:02 (AM). I think
> everyone could agree that it also means 2022-02-22 02:02:00:00, to 2022-02-22
> 02:02:59:59.
>
Not sure how many :59s you want there :) I'm g
Hi Chris, Cameron.
Well, let's say I specify the datetime 2022-02-22 02:02 (AM). I think
everyone could agree that it also means 2022-02-22 02:02:00:00, to
2022-02-22 02:02:59:59.
And I think the same applies for a date. If the pipes are clogged and I
can't take (give) a shit, a shower or do anyt
On Mon, 28 Feb 2022 at 08:51, Cameron Simpson wrote:
>
> On 27Feb2022 11:16, Morten W. Petersen wrote:
> >I was initially using the date object to get the right timespan, but
> >then
> >found that using the right timezone with that was a bit of a pain. So I
> >went for the datetime object instea
On 27Feb2022 11:16, Morten W. Petersen wrote:
>I was initially using the date object to get the right timespan, but
>then
>found that using the right timezone with that was a bit of a pain. So I
>went for the datetime object instead, specifying 0 on hour, minute and
>second.
>
>What's the thinki
Hi.
I'm working on a project where I need to query data for a given year, in
the correct timezone. For accounting purposes.
The code I worked on today is here, see also the version history:
https://github.com/morphex/ethereum-classic-taxman/blob/main/generate_csv.py
I was initially using the d
