Issue498

Title use configurable logging mechanism in translator
Priority wish Status resolved
Superseder Nosy List jendrik, malte
Assigned To Keywords translator
Optional summary

Created on 2014-12-12.14:47:52 by jendrik, last changed by jendrik.

Messages
msg10173 (view) Author: jendrik Date: 2021-03-18.13:52:33
We currently have no plans to pursue this, so I'm closing the issue. Feel free to reopen it when you want to work on this.
msg3912 (view) Author: jendrik Date: 2014-12-12.14:47:52
Split off from issue264 where we made global constants configurable on the commandline. The remaining constants are three DEBUG flags in three 
translator modules.

Quoting Malte:

================================================================================

These are intentionally per-module variables. You usually only want debug output
for one module at a time (the one you're debugging ;-)), so separate options
like "--debug-fact-groups", "--debug-simplify" and "--debug-translate" would
make more sense than a general "--debug".

An alternative solution would be to use a configurable logging mechanism with
subloggers for this. This wouldn't be difficult to set up with the
infrastructure that Python has and would immediately give us some nice
additional benefits. For example, it would immediately give us a "debug flag"
for each module that doesn't currently have one, without cluttering the option
space.

================================================================================
History
Date User Action Args
2021-03-18 13:52:33jendriksetstatus: unread -> resolved
messages: + msg10173
2014-12-12 14:47:52jendrikcreate