16:36:05 <omwb> ChrisWarrick: I'm currently staring at code in `log.py`, where it says "TODO remove in v9". I ask myself and you: "v9" of what? 18:55:03 <ChrisWarrick> omwb: Nikola v9.0.0 18:55:28 <ChrisWarrick> omwb: which is something that isn’t planned for any near future 19:15:15 <KwBot> [nikola] cybervegan opened issue #3759: "plugin" command not working on v8.3.0 https://github.com/getnikola/nikola/issues/3759 19:15:15 <KwBot_> [nikola] cybervegan opened issue #3759: "plugin" command not working on v8.3.0 https://github.com/getnikola/nikola/issues/3759 19:28:10 <KwBot> [nikola] Kwpolska closed issue #3759: "plugin" command not working on v8.3.0 https://github.com/getnikola/nikola/issues/3759 19:28:10 <KwBot_> [nikola] Kwpolska closed issue #3759: "plugin" command not working on v8.3.0 https://github.com/getnikola/nikola/issues/3759 20:16:35 <omwb> Thanks! 20:18:43 <omwb> I'm a bit banging my head with logging. In many Python projects, there are different loggers for different things (often one per class) and one can set LEVEL for any one particular logger one happens to be interested in. That fine convention does not seem to be followed in Nikola, or is it? 20:27:48 <ChrisWarrick> not really, we don’t expose logging controls like this, and I don’t think they’re really useful in a user-facing app 20:29:02 <omwb> I would like to introduce a logger that exposes which templates are executed for which output files. And that can be switched on and off via straightforward configuration, possibly just an env variable. For me, that would be useful. 20:29:32 <ChrisWarrick> that’s what you could use debug logging for 20:29:51 <omwb> Yes. But then I get tons of other stuff I'm not interested in.