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 daniel.urban
Recipients ajaksu2, daniel.urban, eric.araujo, l0nwlf, techtonik
Date 2010-04-30.12:05:56
SpamBayes Score 0.002663089
Marked as misclassified No
Message-id <>
> The point is that your implementation doesn't allow people to generate
> 'Z'-ending timestamp if they need a subset of rfc3339.

That is exactly right. Do you have any suggestion, how to do that? Maybe an optional argument to the rfcformat method? Something like:

def new_rfcformat(self, default_utcoffset='-00:00'):
    if we_know_the_utc_offset:
        return self.rfcformat() # the method in my current patch
        return self.isoformat() + default_utcoffset

This way, if somebody want 'Z' instead of '-00:00', just calls the method like this:


Though this way '+00:00' wouldn't get replaced by 'Z'. 
Any suggestions?
Date User Action Args
2010-04-30 12:05:58daniel.urbansetrecipients: + daniel.urban, techtonik, ajaksu2, eric.araujo, l0nwlf
2010-04-30 12:05:58daniel.urbansetmessageid: <>
2010-04-30 12:05:56daniel.urbanlinkissue7584 messages
2010-04-30 12:05:56daniel.urbancreate