homepage

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 ned.deily
Recipients Connor.Wolf, belopolsky, ned.deily, ronaldoussoren
Date 2014年12月04日.07:54:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1417679645.33.0.574570072601.issue22993@psf.upfronthosting.co.za>
In-reply-to
Content
(Currently, it is not possible to edit a particular message in an issue. You could add a replacement comment to the issue and ask that the older message be delete.)
This seems to be a problem date. As documented, plistlib converts plist dates to/from Python datetime.datetime objects. And, as is documented from datetime objects, the year field must be between 1 (MINYEAR) and 9999 (MAXYEAR). So, it would appear that dates with year 0 are not representable as datetime objects; it's not obvious to me how plistlib could handle a date like that without changing the API, i.e. returning something other than a datetime object or by changing the rules for datetime objects, which is very unlikely to happen.
https://docs.python.org/dev/library/plistlib.html
https://docs.python.org/dev/library/datetime.html#datetime.MINYEAR 
History
Date User Action Args
2014年12月04日 07:54:05ned.deilysetrecipients: + ned.deily, ronaldoussoren, belopolsky, Connor.Wolf
2014年12月04日 07:54:05ned.deilysetmessageid: <1417679645.33.0.574570072601.issue22993@psf.upfronthosting.co.za>
2014年12月04日 07:54:05ned.deilylinkissue22993 messages
2014年12月04日 07:54:04ned.deilycreate

AltStyle によって変換されたページ (->オリジナル) /