pretty undocumented feature (so its not a bug per se).... response.json() is clearly NOT meant to be used in views.... just use json(whatever) instead.
on the "can I call it a bug of not" matter, that seems to surface every once in a while, please take the following as a word of caution (from the initial "heavy pusher" of Continous Integration in web2py)... the (hard ?) truth is that for a project the size of web2py, for all intents and purposes, as long as something is NOT included in the automated tests, you can't call a behavioural change as a bug (or a regression). If something changed and has been introduced in the core code it's because there WASN'T a test for it (or documentation about it in the book) at that time and someone proposed a valid usecase for it (that MAY NOT coincide with the usecase you're used to). In other words, given that: - the change seemed legit - nobody cared to add a test for it - there was no test case for it - it raised no alarms it went merged as a proper fix. Consider also that if you cared to test your app with trunk, you'd have noticed the issue starting from the 17-dec, and could have raised an issue before the stable release. Consider also that if you patch your controller with response.headers['Content-Type'] = 'text/html' before returning, also with the current stable version your issue will be resolved. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
