Ok, at least, I found one setting affects my project. I need set "level" in 
the handler setting to be "NOTSET", instead of "DEBUG" to get 
debug_authorization back as below. But, from my understanding, the "DEBUG" 
level should match the debug log in authdebug_view function. Why doesn't it 
work?

Thanks a lot,
-Shu

diff --git a/code/xxx/yyy/development.ini b/code/xxx/yyy/development.ini
index a0bc00e..607003c 100644
--- a/code/xxx/yyy/development.ini
+++ b/code/xxx/yyy/development.ini
@@ -71,13 +71,13 @@ qualname = sqlalchemy.engine
 [handler_console]
 class = StreamHandler
 args = (sys.stderr,)
-level = DEBUG
+level = NOTSET
 formatter = generic
 
 [handler_filelog]
 class = FileHandler
 args = ('%(here)s/yyy.log','a')
-level = DEBUG
+level = NOTSET
 formatter = generic
 
 [formatter_generic]


On Saturday, February 23, 2013 8:33:56 PM UTC-8, Shu Lin wrote:
>
> I have posted the log in the original post already. Let me paste here 
> also. :-)
>
> Thanks a lot,
> -Shu
>
> # Begin logging configuration
>
>
> [loggers]
>
> keys = root, crossbow_py, sqlalchemy
>
>
> [handlers]
>
> keys = console, filelog
>
>
> [formatters]
>
> keys = generic
>
>
> [logger_root]
>
> level = INFO
>
> handlers = console, filelog
>
>
> [logger_crossbow_py]
>
> level = DEBUG
>
> handlers = 
>
> qualname = crossbow_py
>
>
> [logger_sqlalchemy]
>
> level = INFO
>
> handlers =
>
> qualname = sqlalchemy.engine
>
> # "level = INFO" logs SQL queries.
>
> # "level = DEBUG" logs SQL queries and results.
>
> # "level = WARN" logs neither.  (Recommended for production systems.)
>
>
> [handler_console]
>
> class = StreamHandler
>
> args = (sys.stderr,)
>
> level = NOTSET
>
> formatter = generic
>
>
> [handler_filelog]
>
> class = FileHandler
>
> args = ('%(here)s/crossbow.log','a')
>
> level = NOTSET
>
> formatter = generic
>
>
> [formatter_generic]
>
> format = %(asctime)s %(levelname)-5.5s [%(name)s][%(threadName)s] 
> %(message)s
>
>
> # End logging configuration
>
> On Wednesday, February 20, 2013 6:50:15 AM UTC-8, tonthon wrote:
>>
>> Hi, 
>> maybe providing the log section of your ini file could help to 
>> understand your problem. 
>>
>> Le 19/02/2013 20:05, Shu Lin a �crit : 
>> > Geo, 
>> > 
>> > Sorry, I didn't explain clearly. 
>> > 
>> > Here is the problem. 
>> > 
>> > The crossbow_py is my project, which uses sqlalchemy as a dependent 
>> > library. From python package point of view, pyramid is a dependent 
>> > library also, so as pyramid.authorization. Before,  I could get all 
>> > the logs from sqlalchemy or pyramid.authorization. But, all of sudden, 
>> > log stopped working for those these dependent packages. I can still 
>> > get log in the project itself (crossbow_py) by using crossbow_py as 
>> > the logger. 
>> > 
>> > I guess there is a problem of paste parsing the development.ini. But, 
>> > I don't know why. 
>> > 
>> > Thanks, 
>> > -Shu 
>> > 
>> > On Sunday, February 17, 2013 1:29:21 AM UTC-8, Geo wrote: 
>> > 
>> >     Hi Lin, 
>> > 
>> >     It's hard to understand your questions. The issue is related to 
>> >     authorization log, or sqlalchemy log? What does the covering 
>> >     project mean? 
>> > 
>> > 
>> > -- 
>> > You received this message because you are subscribed to the Google 
>> > Groups "pylons-discuss" group. 
>> > To unsubscribe from this group and stop receiving emails from it, send 
>> > an email to [email protected]. 
>> > To post to this group, send email to [email protected]. 
>> > Visit this group at http://groups.google.com/group/pylons-discuss?hl=en. 
>>
>> > For more options, visit https://groups.google.com/groups/opt_out. 
>> >   
>> >   
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to