Tim, On Sat, Apr 14, 2001 at 06:01:07AM -0400, Tim Peters wrote:

I bet this fresh SF bug report explains it:

http://sourceforge.net/tracker/?func=detail&atid=105470&aid=416089&group_id=5470

Bingo! See the following: $ ./python Python 2.1c1 (#1, Apr 13 2001, 21:47:33) [GCC 2.95.3-2 (cygwin special)] on cygwin_nt-4.01 Type "copyright", "credits" or "license" for more information. >>> import threading Traceback (most recent call last): File "<stdin>", line 1, in ? File "/home/jt/src/Python-2.1c1/Lib/threading.py", line 5, in ? import thread ImportError: No module named thread >>> import threading >>>

Instead they deliver a, umm, bogus module object <wink>. I've never liked this behavior -- but probably can't change it for 2.1 final. It won't be the first time we've needed to worm around it in the test suite either ...

Oh well, there is always 2.2... Thanks, Jason -- Jason Tishler Director, Software Engineering Phone: +1 (732) 264-8770 x235 Dot Hill Systems Corp. Fax: +1 (732) 264-8798 82 Bethany Road, Suite 7 Email: Jason.Tishler@dothill.com Hazlet, NJ 07730 USA WWW: http://www.dothill.com