GNU bug report logs - #63119
date -Ins has a comma!!

Previous Next

Full log

View this message in rfc822 format

From: aaa jjj <ajneu1 <at> gmail.com>
To: 63119 <at> debbugs.gnu.org
Subject: bug#63119: date -Ins has a comma!!
Date: Thu, 27 Apr 2023 16:53:53 +0200

[Message part 1 (text/plain, inline)]

Hi,

is it not a bug, that if I do

LC_ALL=C date -u -Ins

gives me this:
2023-04-27T13:30:15,976772648+00:00

I'm talking about the comma. What is it doing there???
Should this not be a dot instead?

Here's the code:
https://github.com/coreutils/coreutils/blob/35adc746a000ac1f8d1d817a6a3a60d5b80daef5/src/date.c#L465

What does ISO 8601 say about this?

Look at other languages:

node -e 'console.log(new Date().toISOString())'
-> 2023-04-27T13:40:58.846Z

python3 -c 'from datetime import datetime;
print(datetime.now().isoformat())'
-> 2023-04-27T16:23:40.217313

python3 -c 'from datetime import datetime, timezone;
print(datetime.now(timezone.utc).isoformat())'
-> 2023-04-27T14:23:40.228151+00:00

python3 -c 'from datetime import datetime, timezone;
print(datetime.now(timezone.utc).astimezone().isoformat())'
-> 2023-04-27T16:23:40.238908+02:00


PS:
Hell, you cannot simply change it now (backwards-compatibility), but what
about another option flag or whatever...


Thanks.
A

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.