Should be either "+0000" or "UTC" not both. Using Python dateutil: >>> from dateutil.parser import parse >>> parse("2020-05-05 08:46:34 +0000 UTC") Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python3.7/site-packages/dateutil/parser/_parser.py", line 1374, in parse return DEFAULTPARSER.parse(timestr, **kwargs) File "/usr/lib/python3.7/site-packages/dateutil/parser/_parser.py", line 649, in parse raise ParserError("Unknown string format: %s", timestr) dateutil.parser._parser.ParserError: Unknown string format: 2020-05-05 08:46:34 +0000 UTC >>> parse("2020-05-05 08:46:34 +0000") datetime.datetime(2020, 5, 5, 8, 46, 34, tzinfo=tzutc()) >>> parse("2020-05-05 08:46:34 UTC") datetime.datetime(2020, 5, 5, 8, 46, 34, tzinfo=tzutc())
Which feed URL are you looking at?
First seen with: https://packages.gentoo.org/packages/added.atom Updated also: https://packages.gentoo.org/packages/updated.atom
Here's the relevant part from the Atom spec. https://tools.ietf.org/html/rfc4287#section-3.3
(In reply to Mike Gilbert from comment #3) > Here's the relevant part from the Atom spec. > > https://tools.ietf.org/html/rfc4287#section-3.3 It seems here that time.Now() in golang has non-RFC3339 string construction and so when we render time.time objects in the feeds they get the default render that is not RFC3339 compliant. https://play.golang.org/p/RWL2BKn9anw So we need to change how we render dates in the feed templates. -A
This has been fixed some time ago. Thus I'm going to close this bug. Thanks again for pointing this out.