Warning: Can't synchronize with repository "(default)" (Unsupported version control system "svn": No module named svn). Look in the Trac log for more information.

Ticket #2539 (closed task: fixed)

Opened 7 years ago

Last modified 7 years ago

Check that TG 1.5 runs with CherryPy 3.2

Reported by: chrisz Owned by:
Priority: normal Milestone: 1.5
Component: TurboGears Version: 1.5b1
Severity: normal Keywords:
Cc:

Description (last modified by chrisz) (diff)

Check that TG 1.5 runs with CherryPy 3.2 when it has been released (see  this thread).

Do we have to use tools.encode and set tools.encode.encoding = 'utf-8' in the app_cfg.py template?

Change History

comment:1 Changed 7 years ago by chrisz

  • Description modified (diff)

comment:2 Changed 7 years ago by chrisz

Actually the problem seems to be that (at least in CP 3.2rc1) the encode tools is on by default and tries to encode to the first accepted charset which is often latin-1, and not utf-8, even though the response is already encoded as utf-8 by TG. So tools.encode.on = False seems to be the better and more performant solution.

comment:3 Changed 7 years ago by chrisz

Made this and some other changes in r7198-r7203 to make the test suite work with CP 3.2rc1. Needs to be checked again when 3.2 final is out.

comment:4 Changed 7 years ago by chrisz

  • Status changed from new to closed
  • Resolution set to fixed

CherryPy? 3.2 final has been released now and everything is working nicely.

Note: See TracTickets for help on using tickets.