`manage.py syncdb` fails, but what does the error mean?

[chrisbuchholz]

Hey,

I have this django 1.2 app, Snowy[1], that I try to get to run locally. But everytime I do `manage.py syncdb` I get this[2] error, but I have no idea what it means.

Snowy uses, by default django 1.2, python 2 and SQLite3, and at first, I thought it was because that django couldnt talk to SQLite3, but if I create a new django 1.2 app in a python 2 environment, it works fine, so that is not it.

I have no idea what the error means, and the Snowy devs haven't been able to help me out either. I hope some of you guys can.

[1]: http://git.gnome.org/browse/snowy
[2]: http://paste.pocoo.org/show/485318/

// chrisbuchholz

[Martin J. Laubach]

  My guess would be that you named your project directory the same as one of your app directories, that causes all kind of weird import errors.

    mjl

[christoffe...@gmail.com]

As you can see in the source code[1], there is no app inside the
project directory named snowy, so that is not the case.

[1]: http://git.gnome.org/browse/snowy

> --
> 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/-/uKW9j_bqV50J.
> To post to this group, send email to django...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>

[Ramiro Morales]

Your traceback shows you have a weird mixup of paths, both
/home/cb/.virtualenvs/snowy/ and /home/cb/Projects/snowy/
appear as locations of the snowy app.
Perhaps you created a virtualenv with a copy of the app
there but already have a global one?.

Also, is seems the app ships a copy of several third party
django apps (like south) inside their lib/ subdir.

--
Ramiro Morales

[christoffe...@gmail.com]

All right. I have now tried renaming my virtualenv to Snowyv, so no
mix-up would occur. That didn't solve the problem, the error is the
same.
I have not Snowy install globally. The only copy I have of Snowy, is
the one I have in /home/cb/Projects/snowy. I also use virtualenv
(/home/cb/.virtualenvs/snowy), so no mix-up should occur even if I
did, but I don't.

I can understand, from what've said, that some misunderstanding about
the directories and such, is what is going on, but I don't think this
is it, unfortunately.

> --
> You received this message because you are subscribed to the Google Groups "Django users" group.

[christoffe...@gmail.com]

I was too quick there, because just after sending the last email, I
found the problem. It seemed, that the copy of South, that Snowy
bundles in /lib/south, was the culprit. When I deleted it, and
installed south in my virtualenv instead, things started working.

Thank you for your help!