From: "Janko Hauser" <[EMAIL PROTECTED]>
> Zope3 already uses the experimental datetime from Python2.3. From a
> quick look it seems to handle timezones. Perhaps you can look there for
> some ideas or use it instead.
It seems too risky to use experimental features from a version of python
that is
Lennart Regebro wrote:
> From: "Geir Bækholt" <[EMAIL PROTECTED]>
>
>>i can confirm that this is a bug in DateTime.rfc822(), and that
>>rfc-conformant mailclients choke on it aswell..
>
>
> Oh, man, I've looked at DateTime now, and it's a mess... (ar at least, the
> timeone hadnling is). I'm s
From: "Geir Bækholt" <[EMAIL PROTECTED]>
> i can confirm that this is a bug in DateTime.rfc822(), and that
> rfc-conformant mailclients choke on it aswell..
Oh, man, I've looked at DateTime now, and it's a mess... (ar at least, the
timeone hadnling is). I'm seriously considering making rfc822()
Hello Lennart,
Friday, October 11, 2002, 2:00:03 PM, you wrote:
LR> RFC 2822 (which is the currently valid one, if I understand correctly)
LR> specifies the date format to have four digit zone specifications, ie
LR> "GMT+0200", while DateTime.rfc822() happily returns "GMT+2". Not that this
LR>
RFC 2822 (which is the currently valid one, if I understand correctly)
specifies the date format to have four digit zone specifications, ie
"GMT+0200", while DateTime.rfc822() happily returns "GMT+2". Not that this
seems to be any problem, I'm just looking for an answer if this is how it's
supposed
