On Thu, Oct 31, 2019 at 12:23:58PM -0400, Cleber Rosa wrote:
> On Tue, Oct 29, 2019 at 01:14:30PM -0300, Beraldo Leal wrote:
> > Hi all,
> >
> > So, we have a Trello card [1] to discuss what date/time format we are
> > going to adopt when saving date/time on a file.
> >
>
> Hi Beraldo,
>
> I don
On Wed, Oct 30, 2019 at 10:39:02AM -0300, Beraldo Leal wrote:
> On Wed, Oct 30, 2019 at 6:06 AM Amador Pahim wrote:
> > But you can respect the timezone AND avoid ambiguity with "2019-12-01
> > 09:02:52+03:00".
> > As a user, if the timezone is a problem, I would set up my system to
> > GMT. If pa
On Tue, Oct 29, 2019 at 08:43:42PM -0300, Beraldo Leal wrote:
> Hi Amador, my comments below:
>
> On Tue, Oct 29, 2019 at 5:16 PM Amador Pahim wrote:
> > About precision (mentioned in the trello card), no matter the format
> > you pick, it all starts with an epoch on a float with the maximum
> >
On Tue, Oct 29, 2019 at 09:15:57PM +0100, Amador Pahim wrote:
>
> About precision (mentioned in the trello card), no matter the format
> you pick, it all starts with an epoch on a float with the maximum
> precision provided by the platform (time.time()). So one cannot get
> more precise than that,
Hi Cleber, my comments below:
On Thu, Oct 31, 2019 at 1:24 PM Cleber Rosa wrote:
> > 1. Is storage a problem?
>
> I would certainly like to save a few bytes on each message that
> contains a date/time, provided everything else is equal.
>
> But, to be honest, I don't think reading a JSON number
On Tue, Oct 29, 2019 at 01:14:30PM -0300, Beraldo Leal wrote:
> Hi all,
>
> So, we have a Trello card [1] to discuss what date/time format we are
> going to adopt when saving date/time on a file.
>
Hi Beraldo,
I don't think I meant that the date/time format to be discussed and
defined was meant
On Wed, 30 Oct 2019, 18:30 Beraldo Leal wrote:
> On Wed, Oct 30, 2019 at 11:43 AM Amador Pahim wrote:
> > What's the problem with that?
> > 2018-02-16T23:01:00 -03
> > and
> > 2018-02-16T23:01:00 -02
> > Are 1h apart that is pretty clear...
>
> Not a problem, just pointing this particular case.
On Wed, Oct 30, 2019 at 11:43 AM Amador Pahim wrote:
> What's the problem with that?
> 2018-02-16T23:01:00 -03
> and
> 2018-02-16T23:01:00 -02
> Are 1h apart that is pretty clear...
Not a problem, just pointing this particular case.
I prefer to have everything on UTC.
Probably, our configuratio
On Wed, Oct 30, 2019 at 2:39 PM Beraldo Leal wrote:
>
> On Wed, Oct 30, 2019 at 6:06 AM Amador Pahim wrote:
> > But you can respect the timezone AND avoid ambiguity with "2019-12-01
> > 09:02:52+03:00".
> > As a user, if the timezone is a problem, I would set up my system to
> > GMT. If parsing i
On Wed, Oct 30, 2019 at 6:06 AM Amador Pahim wrote:
> But you can respect the timezone AND avoid ambiguity with "2019-12-01
> 09:02:52+03:00".
> As a user, if the timezone is a problem, I would set up my system to
> GMT. If parsing is a problem, I'd setup avocado to "epoch".
> What I fail to see i
On Wed, Oct 30, 2019 at 12:43 AM Beraldo Leal wrote:
>
> Hi Amador, my comments below:
>
> On Tue, Oct 29, 2019 at 5:16 PM Amador Pahim wrote:
> > About precision (mentioned in the trello card), no matter the format
> > you pick, it all starts with an epoch on a float with the maximum
> > precisi
Hi Amador, my comments below:
On Tue, Oct 29, 2019 at 5:16 PM Amador Pahim wrote:
> About precision (mentioned in the trello card), no matter the format
> you pick, it all starts with an epoch on a float with the maximum
> precision provided by the platform (time.time()). So one cannot get
> more
On Tue, Oct 29, 2019 at 5:14 PM Beraldo Leal wrote:
>
> Hi all,
>
> So, we have a Trello card [1] to discuss what date/time format we are
> going to adopt when saving date/time on a file.
>
> I'm moving the discussion here because it seems better to discuss here
> than on Trello.
>
> When it comes
Hi all,
So, we have a Trello card [1] to discuss what date/time format we are
going to adopt when saving date/time on a file.
I'm moving the discussion here because it seems better to discuss here
than on Trello.
When it comes to date/time storage format, I can think of two very
well-used standa
14 matches
Mail list logo
