On Mon, 2014-02-24 at 12:11 +0100, Johan Råde wrote: > > Observed behavior with PyPy: > > Traceback (most recent call last): > File "app_main.py", line 72, in run_toplevel > File "C:\Test\test\test.py", line 1, in <module> > import foo > ImportError: No module named foo
Just shooting in the dark here, but could you please specify how did you build foo more exactly? Back when I was experimenting with CPyExt, I've learned that PyPy will not load foo.so (not sure what the name should be like on Windows) by default, because it doesn't have the right extension, which it will have if it's built with PyPy distutils, but not if you have done this manually with a Makefile. The name should be something like 'foo.pypy-22.so', and the right suffix is defined somewhere in distutils. -- Sincerely yours, Yury V. Zaytsev _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
