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 belopolsky, benjamin.peterson, jamesh, mark.dickinson, vstinner
Date 2010-07-08.00:06:04
SpamBayes Score 0.00010200068
Marked as misclassified No
Message-id <1278547568.64.0.437682297885.issue5288@psf.upfronthosting.co.za>
In-reply-to
Content
C code changes eliminating round-trips between timdelta and int offsets committed in r82642 and Python code changes committed to sandbox in r82641.

Now the requested behavior change is easy and I am about +0.5 on relaxing the offset checks to allow seconds in the offsets and about +0.1 on removing the checks altogether and allowing arbitrary timedeltas even over 1 day.

The only substantive question in my mind is how to handle printing in formats like %z which only provide 4 digits for UTC offset.  Two options seem reasonable: a) truncate sub-minute offsets; and b) follow RFC 3339 recommendation and translate the time into the nearest whole-minute timezone.

I am slightly is favor of (a), but this whole problem may be a reason to reject this RFE.
History
Date User Action Args
2010-07-08 00:06:09belopolskysetrecipients: + belopolsky, jamesh, mark.dickinson, vstinner, benjamin.peterson
2010-07-08 00:06:08belopolskysetmessageid: <1278547568.64.0.437682297885.issue5288@psf.upfronthosting.co.za>
2010-07-08 00:06:07belopolskylinkissue5288 messages
2010-07-08 00:06:04belopolskycreate