In article <mailman.5375.1241962005.11746.python-l...@python.org>, Geoff Gardiner <ggardi...@iee.org> wrote: >Aahz wrote: >> >> What directory are you running this from? What happens if you switch to >> running "python Lib/test/regrtest.py"? Taking a closer look, this looks >> more like a plain import error. > >I couldn't do quite that because there's no Lib, but instead (in Ubuntu >Hardy, this time): >.... >geg...@gegard:~$ cd /usr/lib/python2.5/ >geg...@gegard:/usr/lib/python2.5$ python test/regrtest.py > >9 tests skipped: > test_builtin test_doctest test_doctest2 test_exceptions > test_grammar test_opcodes test_operations test_types test_unittest >Traceback (most recent call last): > File "test/regrtest.py", line 1384, in <module> > main() > File "test/regrtest.py", line 416, in main > e = _ExpectedSkips() > File "test/regrtest.py", line 1321, in __init__ > from test import test_socket_ssl >ImportError: cannot import name test_socket_ssl >geg...@gegard:/usr/lib/python2.5$ > >Also >geg...@gegard:~$ locate */test_socket_ssl.* >geg...@gegard:~$ #returns nothing > >And >geg...@gegard:~$ locate /usr/lib/python2.5/test/test_*.* >/usr/lib/python2.5/test/test_support.py >/usr/lib/python2.5/test/test_support.pyc >geg...@gegard:~$
That seems to demonstrate that regrtest.py is indeed a good mechanism for finding out whether it's a b0rked install! -- Aahz (a...@pythoncraft.com) <*> http://www.pythoncraft.com/ "It is easier to optimize correct code than to correct optimized code." --Bill Harlan -- http://mail.python.org/mailman/listinfo/python-list
