To answer my own question, turns out it's due to the fact that I have
a subdir called "site".
I believe this has some conflicts with Python and leads to this
strange behavior.
After renaming it to something else, the problem goes away.
-Aaron
On Jul 5, 7:13 pm, Aaron <[EMAIL PROTECTED]> wrote:
> So here's something really strange. I ran
>
> Python 2.5.2 (r252:60911, Jun 30 2008, 18:59:56)
> [GCC 3.3.5 (Debian 1:3.3.5-13)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.>>>
> import sys
> >>> sys.path
>
> ['', '/home/user/run/lib/python2.5/site-packages/setuptools-0.6c8-
> py2.5.egg', '/home/user/run/lib/python2.5/site-packages/
> Django-0.97_pre-py2.5.egg', '/home/user/run/lib/python2.5/site-
> packages/MySQL_python-1.2.2-py2.5-linux-i686.egg', '/home/.winkler/
> user', '/home/user/lib/python', '/home/user/soft/django_src', '/home/
> user/django_projects', '/home/user/run/lib/python25.zip', '/home/user/
> run/lib/python2.5', '/home/user/run/lib/python2.5/plat-linux2', '/home/
> user/run/lib/python2.5/lib-tk', '/home/user/run/lib/python2.5/lib-
> dynload', '/home/user/run/lib/python2.5/site-packages']
>
> >>> import MySQLdb
>
> No errors at all. Notice that the MySQL_python-1.2.2 is correctly
> installed in the site-packages via easy install.
>
> Now I cd to myproject directory and ran python manage.py shell
> and I got:
>
> Traceback (most recent call last):
> File "manage.py", line 12, in <module>
> execute_manager(settings)
> File "/home/user/soft/django_src/django/core/management/
> __init__.py", line 272, in execute_manager
> utility.execute()
> File "/home/user/soft/django_src/django/core/management/
> __init__.py", line 219, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
> File "/home/user/soft/django_src/django/core/management/base.py",
> line 72, in run_from_argv
> self.execute(*args, **options.__dict__)
> File "/home/user/soft/django_src/django/core/management/base.py",
> line 86, in execute
> output = self.handle(*args, **options)
> File "/home/user/soft/django_src/django/core/management/base.py",
> line 168, in handle
> return self.handle_noargs(**options)
> File "/home/user/soft/django_src/django/core/management/commands/
> shell.py", line 17, in handle_noargs
> from django.db.models.loading import get_models
> File "/home/user/soft/django_src/django/db/__init__.py", line 17, in
> <module>
> backend = __import__('%s%s.base' % (_import_path,
> settings.DATABASE_ENGINE), {}, {}, [''])
> File "/home/user/soft/django_src/django/db/backends/mysql/base.py",
> line 12, in <module>
> raise ImproperlyConfigured("Error loading MySQLdb module: %s" % e)
> django.core.exceptions.ImproperlyConfigured: Error loading MySQLdb
> module: No module named MySQLdb
>
> Python 2.5.2 (r252:60911, Jun 30 2008, 18:59:56)
> [GCC 3.3.5 (Debian 1:3.3.5-13)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.>>>
> import sys
> >>> sys.path
>
> ['', '', '/home/user/lib/python', '/home/user/soft/django_src', '/home/
> user/django_projects', '/home/user/run/lib/python25.zip', '/home/user/
> run/lib/python2.5/', '/home/user/run/lib/python2.5/plat-linux2', '/
> home/user/run/lib/python2.5/lib-tk', '/home/user/run/lib/python2.5/lib-
> dynload']>>> import MySQLdb
>
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> ImportError: No module named MySQLdb
>
> It looks like the site packages are removed _AFTER_ I ran the python
> manage.py??
>
> Looking at manage.py, it doesn't really do much so I expect somehow
> inside execute_manger it's modifying sys.path??
>
> Any ideas?
>
> -Aaron
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
