On Apr 8, 2008, at 3:41 AM, Marcin Kasperski wrote:
> > > (tested using pylons-dev and WebError-0.8a) > > I have some error in my sources. Unfortunately WebError crashes so I > do not see this error but WebError failure instead. And it crashes > because it .encode-s strings using 'ascii'. > > I tried replacing all 'ascii' with 'utf-8' in > weberror/exceptions/formatter.py and it seems to resolve the issue > (true error was properly shown in pylons debugging page, in this case > it was lacking import) > > The main question: why 'ascii'? Plus ... what about patching WebError > just like I did? > There's a ticket logged about this here: http://pylonshq.com/project/pylonshq/ticket/406 Ideally this would be taken care of before the 0.9.7 release. Is there any similar issues with the EvalException used in 0.9.6.1 I wonder, or is this new due to the new XML generation? The problem isn't just as easy as using utf-8, unfortunately not everybody's source encoding is utf-8. Basically WebError needs to determine the actual source encoding used (there's a patch in the ticket for that), and use that to generate a displayable version. -- Philip Jenvey --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
