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 r.david.murray
Recipients belopolsky, r.david.murray, wiml
Date 2012-06-07.12:48:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1339073329.35.0.91931658187.issue9256@psf.upfronthosting.co.za>
In-reply-to
Content
An alternative is to do what the email package in 3.3 does, and treat naive datetimes as exactly "UTC referenced but with no information as to what local timezone they originated in".  Either way, a program using the plistlib is going to have to know about this and handle the distinction itself, since as you say datetime doesn't have a way to make this differentiation (other than naive vs aware).  So it needs to be documented clearly if it isn't already.
History
Date User Action Args
2012-06-07 12:48:49r.david.murraysetrecipients: + r.david.murray, belopolsky, wiml
2012-06-07 12:48:49r.david.murraysetmessageid: <1339073329.35.0.91931658187.issue9256@psf.upfronthosting.co.za>
2012-06-07 12:48:48r.david.murraylinkissue9256 messages
2012-06-07 12:48:48r.david.murraycreate