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
36635	Settings._explicit_settings attribute not accessible when using override_settings	mmdev		"The `Settings._explicit_settings` attribute, which is always populated by `Settings.__init__()`, becomes inaccessible when the `override_settings` decorator or context manager is used. This causes an `AttributeError` when trying to access this attribute, creating inconsistent behavior.

== Steps to Reproduce

As a decorator:
{{{#!python
from django.test import override_settings
from django.conf import settings

@override_settings(KEY=""VALUE"")
def test_override_settings(settings):
    assert settings._explicit_settings  # Raises AttributeError
}}}

As a context manager:
{{{#!python
from django.test import override_settings
from django.conf import settings

with override_settings(KEY=""VALUE""):
    settings._explicit_settings  # Raises AttributeError
}}}

Both cases raise `AttributeError: '_explicit_settings'` but work correctly without `override_settings`.

== Expected Behavior

The behavior should be consistent: if `_explicit_settings` is accessible without `override_settings`, it should remain accessible when using `override_settings` (both as a decorator and context manager). This attribute is an internal part of the Settings API and may be needed by test code to inspect which settings were explicitly set in the settings module."	Uncategorized	closed	Testing framework	5.2	Normal	wontfix			Unreviewed	0	0	0	0	1	0