Well...
$ /home/wsgi/pypy-1.5/bin/pypy
Python 2.7.1 (b590cf6de419, Apr 30 2011, 02:00:34)
[PyPy 1.5.0-alpha0 with GCC 4.4.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
And now for something completely different: ``yes, but what't the sense of 0
<
"duran duran"''
>>>> import sys,pprint
>>>> pprint.pprint(sys.path)
['',
'/home/wsgi/pypy-1.5/lib_pypy',
'/home/wsgi/pypy-1.5/lib-python/modified-2.7',
'/home/wsgi/pypy-1.5/lib-python/2.7',
'/home/wsgi/pypy-1.5/lib-python/modified-2.7/lib-tk',
'/home/wsgi/pypy-1.5/lib-python/2.7/lib-tk',
'/home/wsgi/pypy-1.5/lib-python/2.7/plat-linux2',
'/home/wsgi/pypy-1.5/site-packages',
'/home/wsgi/pypy-1.5/site-packages/PIL']
>>>>
So you're right, it sees only dirs inside its installation dir. But funny
thing is that directory /home/wsgi/pypy-1.5/site-packages is actually
symlink:
/home/wsgi/pypy-1.5/site-packages -> /usr/share/pyshared/
and it points to the python's site-packages. And that PIL (last entry)
exists in the target directory. So I wonder why on earth it sees only PIL
subdir, from helluva lot of others? Even if I set path manually:
$ export PYTHONPATH=/usr/share/pyshared
$ /home/wsgi/pypy-1.5/bin/pypy
Python 2.7.1 (b590cf6de419, Apr 30 2011, 02:00:34)
[PyPy 1.5.0-alpha0 with GCC 4.4.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
And now for something completely different: ``to save a tree, eat a beaver''
>>>> import pprint, sys
>>>> pprint.pprint(sys.path)
['',
'/usr/share/pyshared',
'/home/wsgi/pypy-1.5/lib_pypy',
'/home/wsgi/pypy-1.5/lib-python/modified-2.7',
'/home/wsgi/pypy-1.5/lib-python/2.7',
'/home/wsgi/pypy-1.5/lib-python/modified-2.7/lib-tk',
'/home/wsgi/pypy-1.5/lib-python/2.7/lib-tk',
'/home/wsgi/pypy-1.5/lib-python/2.7/plat-linux2',
'/home/wsgi/pypy-1.5/site-packages',
'/home/wsgi/pypy-1.5/site-packages/PIL']
>>>>
The same error after that:
$ /home/wsgi/pypy-1.5/bin/pypy manage.py shell
Traceback (most recent call last):
File "app_main.py", line 53, in run_toplevel
File "manage.py", line 2, in <module>
from django.core.management import execute_manager
ImportError: No module named django.core
So I think I'll give up at this point - I now realized that my interest in
pypy come probably too early...
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-users/-/JkpNIjkA3qYJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
