#2238: Server error instead of stack trace when code contains non-ascii chars
------------------------+---------------------------------------------------
 Reporter:  chrisz      |        Owner:       
     Type:  defect      |       Status:  new  
 Priority:  normal      |    Milestone:  2.1  
Component:  TurboGears  |      Version:  2.0b5
 Severity:  major       |   Resolution:       
 Keywords:  weberror    |  
------------------------+---------------------------------------------------
Old description:

> Here is how to reproduce the problem:
>
>  * create a new project with `paster quickstart`
>  * as the first line of `controllers/root.py`, insert: `# -*- coding:
> utf-8 -*-`
>  * in the index controller, insert `flash(u"Hallöle!")` (use a utf-8
> editor)
>  * this should work and display a nice flash message
>  * pretend you made a mistake by removing the `u` in front of the unicode
> string above
>  * now you get a server error without any clue where to search for the
> error
>  * the log output does not help either
>
> This seems to be a problem of weberror (this happened with weberror
> 0.10.1). I was able to work around this by encoding `short_er` and
> `long_er` in `weberror.evalexception.format_eval_html`. It's currently
> not clear to me where weberror is developed, is this part of Pylons? We
> need to get this fixed properly in weberror and make TG2 use the fixed
> version.

New description:

 Here is how to reproduce the problem:

  * create a new project with `paster quickstart`
  * in the index controller, insert `flash(u"Hallöle!")` (and save the file
 with utf-8 encoding)
  * this should work and display a nice flash message
  * pretend you made a mistake by removing the `u` in front of the unicode
 string above
  * now you get a server error without any clue where to search for the
 error
  * the log output does not help either

 This seems to be a problem of weberror (this happened with weberror
 0.10.1). I was able to work around this by encoding `short_er` and
 `long_er` in `weberror.evalexception.format_eval_html`. It's currently not
 clear to me where weberror is developed, is this part of Pylons? We need
 to get this fixed properly in weberror and make TG2 use the fixed version.

-- 
Ticket URL: <http://trac.turbogears.org/ticket/2238#comment:5>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to