Bryan Fullerton([EMAIL PROTECTED])@Fri, Dec 03, 2004 at 07:58:26AM -0500:
>
> Do I need to do something with Mailman after updating to Python 2.4,
> or is this a bug?
Okay, I just did a couple of tests here and after doing a "mailmanctl
restart" I no longer appear to be receiving those traceback
Bryan Fullerton([EMAIL PROTECTED])@Fri, Dec 03, 2004 at 07:58:26AM -0500:
>
> Do I need to do something with Mailman after updating to Python 2.4,
> or is this a bug?
Looks like I'm getting the same thing with Mailman 2.1.4 and Python
2.4, although the mail sent to the lists is reaching the appro
On Fri, 2004-12-03 at 21:41, Tokio Kikuchi wrote:
> time.strftime('%d-%b-%Y', day + (0,)*6)) should be something like:
> time.strftime('%d-%b-%Y', day + (0,0,0,0,1,0))
>
> Looks like we should care 2.4 compatibilty first before jumping in it.
Definitely. We should not release 2.1.6 until we're
Bryan Fullerton wrote:
Howdy,
I'm running Mailman 2.1.5 and upgraded to Python 2.4 yesterday. Since
then I've gotten 9 tracebacks in the error log as below, with ~130
bounces processed during that time. I've never seen this error before
with Mailman that I can remember.
(snip)
Dec 03 07:48:21 2004
Howdy,
I'm running Mailman 2.1.5 and upgraded to Python 2.4 yesterday. Since
then I've gotten 9 tracebacks in the error log as below, with ~130
bounces processed during that time. I've never seen this error before
with Mailman that I can remember.
Dec 03 07:48:21 2004 qrunner(47971): Traceback (m
