Closed ghost closed 10 years ago
I see this is a common error with relation to django debug toolbar version > 0.11.0 and the actual django version. I fixed this..simply using the Explicit setup recomendation of the debug toolbar documentation. This is my commit: http://git.io/9KNgSw ..and I hope this help to future people that need run the project with this versions.
Finally I have question: why you dont writes the specific version of packages in the requirements.txt?..I think is a best practice, for example:
Django==1.6.2 South==0.8.4 ...etc... thanks.
Good catch Nicolas!
Indeed, version pinning is important to have a reproducible deployment environment, please send a functional pullrequest to the neurostars.org branch, and I'll have a look at it.
When I try run the project following the instructions, I get this error:
"django.db.utils.OperationalError: no such table: django_site" I have the correct default.env, and this is my "pip freeze": Django==1.6.2 South==0.8.4 amqp==1.4.4 anyjson==0.3.3 billiard==3.3.0.16 celery==3.1.9 django-celery==3.1.9 django-debug-toolbar==1.0.1 django-markwhat==1.1 django-pipeline==1.3.22 futures==2.1.6 kombu==3.0.13 pytz==2013.9 sqlparse==0.1.11
The complete traceback here: https://gist.github.com/hannicolas/9460328