Message 249676 - Python tracker

➜

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	tjhnson
Recipients	belopolsky, tim.peters, tjhnson
Date	2015-09-03.17:05:56
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1441299956.96.0.114280587962.issue24979@psf.upfronthosting.co.za>
In-reply-to

Content
Thanks for the pointer to #5288. Happy to consolidate there. In my reading of #5094 (from which I pulled your RFC 2822 reference), the justification I found was "For the allowable range, follow the datetime docs as someone might be relying on that specification already". But this didn't explain why it was in the spec in the first place, and that is the decision I thought was arbitrary, not the decision to maintain the restriction. Splitting hairs at this point. Looking forward to the restriction being removed.

Thanks for the pointer to #5288. Happy to consolidate there.

In my reading of #5094 (from which I pulled your RFC 2822 reference), the justification I found was "For the allowable range, follow the datetime docs as someone might be relying on that specification already".  But this didn't explain why it was in the spec in the first place, and that is the decision I thought was arbitrary, not the decision to maintain the restriction. Splitting hairs at this point. Looking forward to the restriction being removed.

History
Date	User	Action	Args
2015-09-03 17:05:57	tjhnson	set	recipients: + tjhnson, tim.peters, belopolsky
2015-09-03 17:05:56	tjhnson	set	messageid: <1441299956.96.0.114280587962.issue24979@psf.upfronthosting.co.za>
2015-09-03 17:05:56	tjhnson	link	issue24979 messages
2015-09-03 17:05:56	tjhnson	create