Some things have broken in django/flup

After adding autoescape stuff to Django svn, at least several things have broken it seems.

Firstly i noticed the problem with ``flat pages``. Instead of seeing my static data, i got ``Unhadled exeption`` in reply. In logs i found following:

2007-12-01 17:39:13: (mod_fastcgi.c.2588) FastCGI-stderr: Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/flup/server/fcgi_base.py", line 558, in run
    protocolStatus, appStatus = self.server.handler(self)
  File "/usr/lib/python2.5/site-packages/flup/server/fcgi_base.py", line 1120, in handler
    write(data)
  File "/usr/lib/python2.5/site-packages/flup/server/fcgi_base.py", line 1062, in write
    assert type(data) is str, 'write() argument must be string'
AssertionError: write() argument must be string

As seen above, error reported by Flup, which is used by Django to run as fastcgi server. Type of data passed to line 1062 is django.utils.safestring.SafeString now and AssertionError is raised.

There's a ticket already created because of this issue, and even reported to flup's author. But there's no solution to the problem as of now.

4 responses to «Some things have broken in django/flup»

 vgs commented, on December 3, 2007 at 11:50 a.m.:

There is 1 solution - to patch flup. It's described in flup's ticket

 denis commented, on December 3, 2007 at 1:28 p.m.:

Yeah, though i think it would be better for Jango to return a ``string``

Post a comment