Re: Wsgi Traceback on Django 1.8

2015-04-09 Thread lzanuz
Hi Tim, You are right, this view use a @cache_page decorator and after cleaned the cache the problem was solved. I would never imagine that I must clean cache on update to 1.8. Sorry by post here, but I touth that was a seriosly bug on wsgi module. By. Em quinta-feira, 9 de abril de 2015 07

Re: Wsgi Traceback on Django 1.8

2015-04-09 Thread Tim Graham
This query came up on IRC a few days ago. I believe it was solved by clearing the site's cache. This is one of the recommended steps in "How to Upgrade Django." https://docs.djangoproject.com/en/dev/howto/upgrade-version/ On Thursday, April 9, 2015 at 1:14:35 AM UTC-4, Curtis Maloney wrote: > >

Re: Wsgi Traceback on Django 1.8

2015-04-08 Thread Curtis Maloney
At a guess, one of your views is returning a string instead of a HttpResponse object. This is the wrong forum for this question. This list is for discussing the development _of_ django, not _with_ django. Your question belongs in django-users. On 9 April 2015 at 14:56, wrote: > > Error on Dja

Wsgi Traceback on Django 1.8

2015-04-08 Thread lzanuz
Error on Django 1.8: My site do not use session and cookies, its basic a static site and some forms. Django 1.7.7 it's OK. Traceback (most recent call last): File "/usr/local/envs/wscep/lib/python3.4/site-packages/django/core/handlers/wsgi.py", line 195, in __call__ for c in response