On 06/29/2013 11:24 PM, Skip Montanaro wrote: [cut]
that version of Python was executed. Accordingly, /opt/local/lib/python2.7/site-packages was in sys.path, as it should have been. It appears that the generated pypy-c wound up with that directory in its sys.path as well. I wasn't executing it from an installed location. I just set up an alias to execute it from the goal directory. OTOH, perhaps I should build it using /usr/bin/python:
Do you by chance see this warning message when you start your pypy? debug: WARNING: Library path not found, using compiled-in sys.path. debug: WARNING: 'sys.prefix' will not be set. debug: WARNING: Make sure the pypy binary is kept inside its tree of files. debug: WARNING: It is ok to create a symlink to it from somewhere else. 'import site' failed If so, it means that somehow pypy does not find its stdlib and it just uses the builtin sys.path. Note that if you run pypy from within the hg checkout, this should not happen.