New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
plistlib can't decode date from year 0 #85255
Comments
On macOS 10.5.5: /tmp $ defaults export com.apple.security.KCN - import plistlib
import subprocess
if __name__ == "__main__":
plist = subprocess.check_output(["defaults", "export", "com.apple.security.KCN", "-"])
print(plistlib.loads(plist, fmt=plistlib.FMT_XML))
/tmp $ python3.8 plist_date_reduction.py
Traceback (most recent call last):
File "plist_date_reduction.py", line 8, in <module>
print(plistlib.loads(plist, fmt=plistlib.FMT_XML))
File "/usr/local/Cellar/python@3.8/3.8.3/Frameworks/Python.framework/Versions/3.8/lib/python3.8/plistlib.py", line 1000, in loads
return load(
File "/usr/local/Cellar/python@3.8/3.8.3/Frameworks/Python.framework/Versions/3.8/lib/python3.8/plistlib.py", line 992, in load
return p.parse(fp)
File "/usr/local/Cellar/python@3.8/3.8.3/Frameworks/Python.framework/Versions/3.8/lib/python3.8/plistlib.py", line 288, in parse
self.parser.ParseFile(fileobj)
File "/private/tmp/python@3.8-20200527-50093-16hak5w/Python-3.8.3/Modules/pyexpat.c", line 461, in EndElement
File "/usr/local/Cellar/python@3.8/3.8.3/Frameworks/Python.framework/Versions/3.8/lib/python3.8/plistlib.py", line 300, in handle_end_element
handler()
File "/usr/local/Cellar/python@3.8/3.8.3/Frameworks/Python.framework/Versions/3.8/lib/python3.8/plistlib.py", line 376, in end_date
self.add_object(_date_from_string(self.get_data()))
File "/usr/local/Cellar/python@3.8/3.8.3/Frameworks/Python.framework/Versions/3.8/lib/python3.8/plistlib.py", line 254, in _date_from_string
return datetime.datetime(*lst)
ValueError: year 0 is out of range |
There is no year 0. It does not exist. The year after 1 BC is the year 1 AD. |
By the way most datetime libraries will give you incorrect values for dates before 1582, 1752, 1926, 1949 or any dates in that range depending on your country and the predominant religion of your country, county, state, or principality. Dates before 1970 are generally problematic unless the date format also references a calendar system. It's ... messy. |
Year 0 does exist in ISO 8601 though, but that wouldn't help us here as year 0 in that standard is year 1 BCE which is not representable in Python's datetime module. I'm not sure what we can do about this. The best we could do with plistlib is probably to add an option to either set unrepresentable dates to None or represent those dates as strings. A more comprehensive fix is to change datetime to be able to represent these dates, but that's a much larger change that likely requires a PEP. |
You're correct that there is no year 0, but as you see Apple does use <date>0000-12-30T00:00:00Z</date> in their plists. I did not set that in order to test plistlib; it's what I found on my system. If it's a goal that plistlib be able to parse system-generated plists and round-trip them to an equivalent serialization -- and I think that should be a goal -- then using strings or None also won't work. Maybe there could be a plistlib.Datetime for dates which are outside what datetime can represent? |
This hasn't been accepted and opened still for three years and also is likely a change that would require a PEP and no PEP addressing this hasn't been created. IMHO this should be closed. |
Jumping into the discussion here... I looked into this a few months ago and subscribed to this issue, but never actually commented. The short explanation is: according to Apple, this date is actually 01 January 0001 AD/CE. If you use Apple's plutil -p com.apple.security.KCN.plist
{
"absentCircleWithNoReason" => 0
"applicationDate" => 0001-01-01 00:00:00 +0000
"lastCircleStatus" => -1
"lastWritten" => 2019-10-15 17:23:33 +0000
"pendingApplicationReminder" => 4001-01-01 00:00:00 +0000
"pendingApplicationReminderInterval" => 86400
} I don't remember all the messy details, but the Apple/macOS date representation ( Regardless of how it's written, this particular date is relevant because it's the value of re. the last comment: extending the range of |
Sorry didn't catch the part of changing behavior that would be modifying current behavior by changing round-tripping. |
This issue should IMHO not be closed. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: