This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Elvis.Pranskevichus
Recipients Anders.Hovmöller, Arfrever, Elvis.Pranskevichus, Eric.Hanchrow, Roman.Evstifeev, SilentGhost, aymeric.augustin, barry, belopolsky, berker.peksag, cben, cvrebert, davydov, deronnax, eric.araujo, flying sheep, jcea, jstasiak, jwilk, karlcow, kirpit, larsonreever, martin.panter, mcepl, mihaic, nagle, ncoghlan, pbryan, perey, piotr.dobrogost, r.david.murray, roysmith, sirex, vstinner
Date 2017-10-24.23:44:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I think that both the pyiso8601 and boxed/iso8601 implementations parse ISO 8601 strings incorrectly.  The standard explicitly says that all truncated datetime strings are *reduced accuracy timestamps*.  In other words, "2017-10" is *not* equal to "2017-10-01".  Instead, "2017-10" represents the whole month of October 2017.  Same thing with hours.  Earlier versions of ISO 8601 even allowed dropping the year: "--10-01", which meant October 1st of _any year_.  They dropped this from more recent revisions of the standard.

The only place where the truncated representation means "default to zero" is the timezone offset, so "10:10:00+4" and "10:10:00+04:00" mean the same thing.
Date User Action Args
2017-10-24 23:44:49Elvis.Pranskevichussetrecipients: + Elvis.Pranskevichus, barry, jcea, cben, roysmith, ncoghlan, belopolsky, nagle, vstinner, jwilk, mcepl, eric.araujo, Arfrever, r.david.murray, davydov, cvrebert, karlcow, SilentGhost, perey, flying sheep, mihaic, aymeric.augustin, Roman.Evstifeev, berker.peksag, martin.panter, piotr.dobrogost, kirpit, Anders.Hovmöller, jstasiak, Eric.Hanchrow, deronnax, pbryan, sirex, larsonreever
2017-10-24 23:44:49Elvis.Pranskevichussetmessageid: <>
2017-10-24 23:44:49Elvis.Pranskevichuslinkissue15873 messages
2017-10-24 23:44:49Elvis.Pranskevichuscreate