Author r.david.murray
Recipients barry, r.david.murray, timb07
Date 2017-06-19.17:33:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1497893602.75.0.210458109797.issue30681@psf.upfronthosting.co.za>
In-reply-to
Content
I'll make one argument in favor of retaining the exception, and if that doesn't fly then I agree to the solution and will try to review the PR soon.

The argument is this: if parsedate_to_datetime raises an error, you get information about *why* the date was invalid, which you don't get from a 'None' return.  It is my thought that this would be the most useful behavior for the cases where you call it directly (otherwise, why call it directly?)

(And as far as the doc issue goes, you are correct Barry that the current docs don't document the difference in the error case; I noted in another issue that that "should be fixed"...which is only the case now if you agree to my argument above :)
History
Date User Action Args
2017-06-19 17:33:22r.david.murraysetrecipients: + r.david.murray, barry, timb07
2017-06-19 17:33:22r.david.murraysetmessageid: <1497893602.75.0.210458109797.issue30681@psf.upfronthosting.co.za>
2017-06-19 17:33:22r.david.murraylinkissue30681 messages
2017-06-19 17:33:22r.david.murraycreate