By "no traceback" do you mean you're not getting the debug web page when your web application has an internal server error? If that is what you mean, make sure your .ini file has the "set debug" line set to true (make sure to not set this in a production environment).
Although I don't have a lot of experience in magic encoding comments, a quick google search leads me to the possibility that you have some sort of statement (probably towards the top) of your mako template (also check the templates that it inherits) that could be something similar to: <?xml version="1.0" encoding="utf-8"?> or something similar and then you also have a statement similar to this (a magic encoding comment): # -*- coding: utf-8 -*- And the compiler is telling you it doesn't like having both of those in one mako template. So some where in your mako template (and the templates it inherits) you are stating the files encoding twice, Python doesn't like that. Does that help? Let me know. -Dave On Feb 5, 7:21 am, Alexander Zhabotinskiy <[email protected]> wrote: > I'm using pylons 1.0 and when I had an error at my template I'm always > get "Internal Server Error", no traceback. What's wrong in > configuration? > > In the console: > > encoding = util.parse_encoding(fp) > File "C:\Python26\lib\site-packages\mako-0.3.4-py2.6.egg\mako > \util.py", line 213, in > parse_encoding > "python refuses to compile code with both a UTF8" \ > SyntaxError: python refuses to compile code with both a UTF8 byte- > order-mark and a magi > c encoding comment -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. 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.
