|
|
On 2021-07-30 2:29 PM (-4), clipka wrote:
>
> - When users see a date or time, they will usually expect it to indicate
> local time. To achieve that, the parameter passed to `datetime()` would
> have to be of local time flavor.
>
> This speaks heavily in favor of making `now` return local time, as
> opposed to UTC.
>
>
> I think it can be argued that local time is of far more relevance to
> most users than UTC.
>
> [snip]
>
> Actually, no - in this case `now` returning local time is not a
> Unix/Linux bug (or, more to the point, not a "boost on Unix/Linux bug"),
> but rather proper intrinsic behavior of the new implementation I chose.
>
> I realize only now that I accidently implemented the wrong behavior
> (judging by the documentation, and intent so far).
The 3.8 documentation say 'now' should return GMT, and on my GNU/Linux
box, it (pre-beta) does return UTC or GMT. Are you proposing a change
in behavior?
Post a reply to this message
|
|