Just to bump this a bit... I'm contemplating that maybe we shouldn't do database logging.warnings at all. We could just collect a list of drivers that we were able to import and later just display that as 'Database drivers available: %s'. That would perhaps also a bit less confusing for new users who think that the db exceptions at web2py startup are actually errors (we could still keep them, but with lower priority, logging.debug probably, so it doesn't get in the way of debugging).
On Nov 6, 8:48 pm, achipa <[EMAIL PROTECTED]> wrote: > Ok, ok :) I made a small one for myself but my 'problem' is that > gluon.sql gets imported quite early on, long before any cmdline params > get interpreted, so the db import warnings always pop up. Any ideas > how to get around this elegantly ? > > mdipierro wrote: > > Send me a patch! > > > On Nov 6, 10:11 am, achipa <[EMAIL PROTECTED]> wrote: > > > I'd propose the introduction of two new command line switches. What > > > are your thoughts on this ? I'd like to see > > > > a) --debug=debuglevel (which would set that numeric level throughout > > > web2py and the logging module would act accordingly without the need > > > to modify code or fiddle with the environment) > > > > b) --quiet(which would disable all output, making it more convenient > > > to run from scripts in combination with the -M -S options) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
