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:

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:

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.

[Mariusz Felisiak]

_explicit_settings is an undocumented, internal, implementation detail. You should not rely on it.