Why is the default logger overridden?

https://github.com/cocotb/cocotb/blob/ba0fb097efbd2939ad6a961ee8d02793104ef8f7/cocotb/__init__.py#L60

How about instead of forcing users to use the cocotb logger through logging, we just extend cocotb.log to act more like the logging module and get users to use that instead?

[eric-wieser]

would first try to load a user’s custom logger module

I think we just leave this to the python logging infrastructure.

I’d like to see this pattern be applied to the embed_gpi/cocotb module entry point as well, so we could overload the entire (or at least part) of the setup to support launching into IPython.

Filed #1225 for that to keep discussion here focused

Maybe some documentation on required interfaces.

Once #1213 is in, the answer will basically be “there is no cocotb logging interface, just configure the python logging module as you see fit”.

[ktbarrett]

We need the ability to inject a Logger class before the cocotb, gpi, scheduler, and regression loggers are constructed, or there will be inconsistent logging behavior, no? Currently no user code is run until the user’s test module is loaded.