id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
33920	Document that LOGGING_CONFIG callback is not called when LOGGING dict is not set.	Craig de Stigter	Kinza-Raza	"
the docs say:

{{{
LOGGING_CONFIG¶

Default: 'logging.config.dictConfig'

A path to a callable that will be used to configure logging in the Django project. Points at an instance of Python’s dictConfig configuration method by default.

If you set LOGGING_CONFIG to None, the logging configuration process will be skipped.
}}}

https://docs.djangoproject.com/en/4.1/ref/settings/#logging-config


It turns out that in fact, you need to set LOGGING to some non-falsey value for the LOGGING_CONFIG callback to even be called at all. This isn't obvious - part of the reason for having a callback is if your logging is more dynamic than a dict-based config allows.

So now all our apps need some variation of this to work around this bug:

{{{
#!python
LOGGING = {""note"": ""this MUST be a non-falsey value for logging to work""}
}}}

I think this dependency on LOGGING should be clearly stated in the documentation for LOGGING_CONFIG, or just fixed (by always calling the `LOGGING_CONFIG` function even if `LOGGING` is falsey)
"	Cleanup/optimization	closed	Core (Other)	dev	Normal	fixed		Claude Paroz Daniele Procida	Ready for checkin	1	0	0	0	0	0