On Mar 11, 7:55 pm, Malcolm Tredinnick <malc...@pointy-stick.com>
wrote:
> On Wed, 2009-03-11 at 14:50 -0700, Steve Chervitz Trutane wrote:
> > I believe I may have hosed my django installation while I was trying
> > to get up and running with Pinax.  I'm working from the django trunk
> > (1.1alpha) on linux. Here's what happens now when I try to fire up a
> > new django project (a la the turorial):
>
> > $ django-admin.py startproject mysite
> > $ cd mysite
> > $ python manage.py runserver
> > Validating models...
> > Unhandled exception in thread started by <function inner_run at
> > 0xb7aacf0c>
> > Traceback (most recent call last):
> >   File "/home/teamhuma/tools/django-trunk/django/core/management/
> > commands/runserver.py", line 48, in inner_run
> >     self.validate(display_num_errors=True)
> >   File "/home/teamhuma/tools/django-trunk/django/core/management/
> > base.py", line 249, in validate
> >     num_errors = get_validation_errors(s, app)
> >   File "/home/teamhuma/tools/django-trunk/django/core/management/
> > validation.py", line 22, in get_validation_errors
> >     from django.db import models, connection
> >   File "/home/teamhuma/tools/django-trunk/django/db/__init__.py", line
> > 53, in <module>
> >     'TIME_ZONE': settings.TIME_ZONE,
> >   File "/home/teamhuma/lib/python2.6/site-packages/django/db/backends/
> > dummy/base.py", line 45, in __init__
> >     super(DatabaseWrapper, self).__init__(*args, **kwargs)
> > TypeError: object.__init__() takes no parameters
>
> I believe you just updated to the latest subversion trunk and are
> running MySQL and encountered a bug that was fixed in r10030. The error
> is being reported from a piece of code that changed heavily yesterday
> (literally, about 24 hours ago as I write this) and there were some
> side-effects that were still being sorted out over the next few hours.
>
> If that's not your situation, pleaes provide some details about database
> backend, Django version, etc.

My error goes away when using the official Django release (1.0.2)
rather than the current trunk (r10032).

As for the backend, I have not altered the settings.py that django-
admin.py startproject created, so my DATABASE_ENGINE is not defined
when I get the error I reported above.

But I do run into a MySQL issue when I specify mysql as the db engine
and install mysql support for my python using `easy_install mysql-
python':

$ cd mysite
$ python manage.py runserver
Validating models...
Unhandled exception in thread started by <function inner_run at
0xb7a815a4>
Traceback (most recent call last):
  File "/home/teamhuma/tools/django-official/django/core/management/
commands/runserver.py", line 48, in inner_run
    self.validate(display_num_errors=True)
  File "/home/teamhuma/tools/django-official/django/core/management/
base.py", line 246, in validate
    num_errors = get_validation_errors(s, app)
  File "/home/teamhuma/tools/django-official/django/core/management/
validation.py", line 22, in get_validation_errors
    from django.db import models, connection
  File "/home/teamhuma/tools/django-official/django/db/__init__.py",
line 16, in <module>
    backend = __import__('%s%s.base' % (_import_path,
settings.DATABASE_ENGINE), {}, {}, [''])
  File "/home/teamhuma/tools/django-official/django/db/backends/mysql/
base.py", line 13, in <module>
    raise ImproperlyConfigured("Error loading MySQLdb module: %s" % e)
django.core.exceptions.ImproperlyConfigured: Error loading MySQLdb
module: /lib/tls/libc.so.6: version `GLIBC_2.4' not found (required
by /home/teamhuma/.python-eggs/MySQL_python-1.2.3b1-py2.6-linux-
i686.egg-tmp/_mysql.so)


I can avoid this problem if I install MySQL-python-1.2.2 from the
distribution (gotten from 
http://sourceforge.net/project/showfiles.php?group_id=22307).

So I'm good to go for now, content to stick with django 1.0.x until
1.1 stabilizes. For the record, I was also able to get the Pinax basic
project running from the pinax trunk, deployed with fcgi at
http://pinax-basic.teamhuman.org

Steve
--~--~---------~--~----~------------~-------~--~----~
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 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to