On Sun, 2010-09-12 at 23:40 -0700, Mike Orr wrote: >> >> Probably should still live in INI file. > >>> I suppose a logging configuration may not belong in the minimal >>> application, but in that case I'd have to provide the code to paste >>> in. (Maybe using paste.translogger as a sample middleware that uses >>> logging.) >>> >>> On the other hand, it can be argued that logging is so central to >>> everything, it belongs in the minimal application. >>> Especially because libraries may log, and there really should be >>> handlers and formatters already set up for it in that case. >> >> Should be fine to add that configuration there. > > I guess that means myapp/__init__.py will have to initialize the > logging. Because who else will?
I figured it would just go in the .ini file as before, and PasteDeploy would initialize it as always. > This might be good to make the logging activation explicit. One > problem with "paster serve" is nobody can figure out where logging is > activated or why it doesn't automatically work with "paster shell" or > custom commands. It gives the impression that Paste activates the > logging as a basic Paste service, but it doesn't, "paster serve" or > something below it does. Stdlib logging configuration is horrid, no matter how you slice it really. Maybe just a little howto for paster shell about how to configure logging explicitly from the development.ini file? - C -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-de...@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
