This is not wholly surprising, but py.test doesn't appear to run from an egg. (I say it's not surprising, given that py is doing its own import trickery...) The way it fails is interesting. I can import py from a python prompt, but not from the py.test script. /usr/local/bin/python Python 2.4.1 (#2, Mar 31 2005, 00:05:10) [GCC 3.3 20030304 (Apple Computer, Inc. build 1666)] on darwin Type "help", "copyright", "credits" or "license" for more information.
import py.test
py.test py lib is at /Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/py-0.8.0_alpha1-py2.4.egg/py/__init__.pyc Traceback (most recent call last): File "/usr/local/bin/py.test", line 4, in ? pkg_resources.run_main('py==0.8.0-alpha1', 'py.test') File "build\bdist.win32\egg\pkg_resources.py", line 110, in run_main File "build\bdist.win32\egg\pkg_resources.py", line 599, in run_script File "/Library/Frameworks/Python.framework/Versions/2.4/bin/py.test", line 3, in ? import pkg_resources ImportError: cannot import name py Another of the pylib scripts, py.countloc, works fine. That one may not depend on the rest of the package, though. I'd thought I'd toss this out there in case anyone cares, but I'm not sure if anyone will care about this particular case. Kevin