Message 106977 - 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	belopolsky
Recipients	ajaksu2, belopolsky, brett.cannon, doerwalter, eric.araujo, ggenellina, kawai, mark.dickinson, pitrou, rafe, vstinner
Date	2010-06-03.19:50:44
SpamBayes Score	0.0066436203
Marked as misclassified	No
Message-id	<AANLkTimLSg_zzF2o_vIsKRdWXapDY0GS5uJfyz3GwiBL@mail.gmail.com>
In-reply-to	<AANLkTim0ksjD71bZDANdWxVAHyetQUQ48FBVqc67lse3@mail.gmail.com>

Content
On Thu, Jun 3, 2010 at 3:41 PM, Alexander Belopolsky <report@bugs.python.org> wrote: .. > I am not sure. At this stage treat 12 as a placeholder for whatever > the relevant standard says. Believe it or not, at least one standard, RFC 2822, allows any offset representable as HHMM: "the zone MUST be within the range -9959 through +9959" <http://tools.ietf.org/html/rfc2822.html>. I am inclined to simply remove any range checking and allow arbitrary timedelta as an offset.

On Thu, Jun 3, 2010 at 3:41 PM, Alexander Belopolsky
<report@bugs.python.org> wrote:
..
> I am not sure.   At this stage treat 12 as a placeholder for whatever
> the relevant standard says.

Believe it or not, at least one standard, RFC 2822, allows any offset
representable as HHMM: "the zone MUST be within the range -9959
through +9959" <http://tools.ietf.org/html/rfc2822.html>.

I am inclined to simply remove any range checking and allow arbitrary
timedelta as an offset.

History
Date	User	Action	Args
2010-06-03 19:50:46	belopolsky	set	recipients: + belopolsky, doerwalter, brett.cannon, mark.dickinson, ggenellina, pitrou, vstinner, ajaksu2, kawai, eric.araujo, rafe
2010-06-03 19:50:44	belopolsky	link	issue5094 messages
2010-06-03 19:50:44	belopolsky	create