[Mailman-Users] Installing python upgrade - will this failed test affect Mailmain?

[Scott Brown]

I went to install Mailman 2.0 today, and found I needed to upgrade Python as
well. (I was only running 1.5.1, and the docs say 1.5.2 or better).  My
server is not-so-up-to-date - it's still running RH 5.4

So first I tried installing Python 2.0 - I figured might as well go full
hog - and got 2 failed tests on it.

So I then tried Python 1.6 to see if that would be any closer to working.
One failed test. this time.

[root at apollo /home/webmaster/Python-1.6/Lib]# ../python
../Lib/test/test_strftime.py
strftime test for Sat Nov 25 20:29:38 2000
Strftime test, platform: linux2, Python version: 1.6
Supports nonstandard '%c' format (near-asctime() format)
Supports nonstandard '%x' format (%m/%d/%y %H:%M:%S)
Supports nonstandard '%Z' format (time zone name)
Supports nonstandard '%D' format (mm/dd/yy)
Supports nonstandard '%e' format (day of month as number, blank padded
 0-31))
Supports nonstandard '%h' format (abbreviated month name)
Supports nonstandard '%k' format (hour, blank padded ( 0-23))
Supports nonstandard '%n' format (newline character)
Supports nonstandard '%r' format (%I:%M:%S %p)
Supports nonstandard '%R' format (%H:%M)
Does not appear to support '%s' format (seconds since the Epoch in UCT)
Supports nonstandard '%t' format (tab character)
Supports nonstandard '%T' format (%H:%M:%S)
Conflict for nonstandard '%3y' format (year without century rendered using
fieldwidth):
  Expected 000, but got y
Conflict for %W (week number of the year (Mon 1st)):
  Expected 09, but got 08
Conflict for %W (week number of the year (Mon 1st)):
  Expected 09, but got 08
Conflict for %W (week number of the year (Mon 1st)):
  Expected 09, but got 08
etc... (about 100 more likes of the same sort of thing...)

My quesiton is, with this %W Conflict, Is this going to throw Mailman
problems?  Or should I go right back to 1.5.2 and hope it installs/tests
fine?