cpython/Lib/test/test_imaplib.py

import imaplib
import time

# We can check only that it successfully produces a result,
# not the correctness of the result itself, since the result
# depends on the timezone the machine is in.

timevalues = [2000000000, 2000000000.0, time.localtime(2000000000),
              '"18-May-2033 05:33:20 +0200"']

for t in timevalues:
    imaplib.Time2Internaldate(t)
Check for time.struct_time in addition to tuples. Use 3 characters for zone hours. Fixes #499169. 2002-01-05 07:31:49 -04:00			`import imaplib`
Reverting this to rev 1.3. It's apparently broken everywhere at rev 1.6, and pierslauder didn't respond to email about it on Monday. 2002-07-31 13:42:33 -03:00			`import time`
Check for time.struct_time in addition to tuples. Use 3 characters for zone hours. Fixes #499169. 2002-01-05 07:31:49 -04:00
revert to version 1.2 2002-08-03 08:14:43 -03:00			`# We can check only that it successfully produces a result,`
			`# not the correctness of the result itself, since the result`
			`# depends on the timezone the machine is in.`
Alter text test arg to obey new rule, also include inverse test to make time-zone independant 2002-06-17 04:06:24 -03:00
revert to version 1.2 2002-08-03 08:14:43 -03:00			`timevalues = [2000000000, 2000000000.0, time.localtime(2000000000),`
I don't know what's going on with this test, but the last change from Piers obviously couldn't have passed on any platform. Fiddling it so it works (for a meaning of "works" no stronger than "doesn't fail" <wink>). 2002-08-04 03:53:18 -03:00			`'"18-May-2033 05:33:20 +0200"']`
Check for time.struct_time in addition to tuples. Use 3 characters for zone hours. Fixes #499169. 2002-01-05 07:31:49 -04:00
			`for t in timevalues:`
revert to version 1.2 2002-08-03 08:14:43 -03:00			`imaplib.Time2Internaldate(t)`