> Why not just using the logging module with well-defined categories? First, because the logging module doesn't have categories, only "levels". The categories in Dejavu (IO, SQL, SANDBOX) and CP (access log vs "everything else") aren't heirarchical.
Second, because then CP is taking a stand I don't think it should take, which is "if you want to log CP events, you must use Python's builtin logging module". There are plenty of people who think the stdlib module is overengineered, and "doesn't scale down very well". See http://www.mechanicalcat.net/richard/log/Python/Simple_usage_of_Python_s_logging_module for example. It certainly doesn't support cooperative logging very well, IMO. At the level of TG, this isn't a huge issue, since you can pick a standard. But CP should probably not force it. To put it another way, how would you feel if CP standardized on easylog or twisted.log? To avoid those debates, I think libraries should be "event faucets" that have a simple interface, not tied to any logging "sink" framework. But I'll write a stdlib-logging implementation today to find out if I'm wrong. ;) Robert Brewer System Architect Amor Ministries [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk -~----------~----~----~----~------~----~------~--~---
