Ok. I found my problem, or at least a fix.
It seems that the paste.translogger middleware was automagically being
used in previous versions of pylons. But 0.9.3 doesn't automagically
do this for you.
To fix this, I edited my middleware.py file ->
from paste.translogger import TransLogger
# in make_app
app = TransLogger(app)
TransLogger without any additional arguments simply logs to the
console, which works for me while hacking away in dev mode. Maybe the
template generator should be updated to generate the `correct'
TransLogger entry in the middleware.py file?
jw
On Dec 16, 7:51 pm, "programmer.py"
<prog...@public.gmane.org> wrote:
Yeah I do have debugging on. I'll upgrade and see if it comes back.
jw
On Dec 15, 5:50 pm, "Pedro Algarvio, aka, s0undt3ch"
<u...-beLbHzoLccIdnm+yROf...@public.gmane.org>
wrote:
I'm using 0.9.3 and log entries still get spit on the console, I have
debug enabled, do you?
6 messages in com.googlegroups.pylons-discussRe: Pylons 0.9.2 - where did my loggi...