I thinks this was more related to an update from appengine backend.

Another of my projects without warm up requests crashed the same and fixed 
the same. It was working previously with no inconvenient and suddenly both 
projects threw 500's because of this encoding declaration in-between the 
last two days.

.
CC

On Wednesday, August 12, 2015 at 3:30:59 PM UTC-5, Chuy Cepeda wrote:
>
> Hello, just wanted to share something I just experienced.
>
> I have an appengine app running on python and for several notifications in 
> spanish I use a messages.py file which is loaded in almost every handler. 
> This file gave me no issues given it wasn't containing any specification 
> for encoding. It consists in several lines practically identical to the 
> following:
>
> user_pass_mismatch = unicode('El usuario y contraseƱa no coinciden. Por 
>>> favor intenta de nuevo.','utf-8')
>>
>>
> It gave me no issues while running my app for several months, but lately I 
> just added a set of warmup requests and it started giving 500 errors all 
> the way because of:
>
> SyntaxError: Non-ASCII character '\xc3' in file messages.py on line 1, but 
>> no encoding declared; see http://www.python.org/peps/pep-0263.html for 
>> details
>
>
> Of course, adding the header *# -*- coding: utf-8 -*-* solved the issue, 
> but the weird behavior is that non-resident (non warmup) instances caused 
> no trouble even they didn't specified the encoding declaration.
>
> Best,
>
> Chuy 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/1ff0bbf3-e4b5-4476-bfda-da816dc7d141%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to