Comment 2 for bug 483856

Thanks Andre` for the report.
The bug actually was in sf-django-utils, as you find out with your fix.
Now it *should* work with both Django post- and pre- r11636. Andre`, could you please confirm this with trunk?

Regarding the long name, it bugs me too, but I'm not sure on how to handle this. I believe we need the nested directory structure, since we make use of the package mechanisms from setuptools (so we can provide package integrations with separate eggs, for example). Maybe we could change the package name in setup.py to something shorter (like "sf_django_utils", ...). What's your opinion on this matter?