Message104631
> 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
else:
return self.isoformat() + default_utcoffset
This way, if somebody want 'Z' instead of '-00:00', just calls the method like this:
d.new_rfcformat('Z')
Though this way '+00:00' wouldn't get replaced by 'Z'.
Any suggestions? |
|
Date |
User |
Action |
Args |
2010-04-30 12:05:58 | daniel.urban | set | recipients:
+ daniel.urban, techtonik, ajaksu2, eric.araujo, l0nwlf |
2010-04-30 12:05:58 | daniel.urban | set | messageid: <1272629158.17.0.0182107347575.issue7584@psf.upfronthosting.co.za> |
2010-04-30 12:05:56 | daniel.urban | link | issue7584 messages |
2010-04-30 12:05:56 | daniel.urban | create | |
|