Can't load 'settings.toml' values

[tjnd89]

I'm using dynaconf 3.1.12 under Python 3.9.

I'm having an issue (similar to others that have been reported) where dynaconf doesn't seem to find/load my settings.toml file.

EDIT Note: It appears to be loading the file, but not merging the settings (see my later comments).

My code is structured like this:

my_pkg
    my_pkg
        scripts
            run_me.py
        config.py
        __init.py
        settings.toml

where config.py creates the settings object using

import os
from dynaconf import Dynaconf

ROOT_PATH = os.path.dirname(os.path.realpath(__file__))

settings = Dynaconf(
    envvar_prefix="DYNACONF",
    settings_file="settings.toml",
    root_path=ROOT_PATH
)

as recommended at #374 (comment) to work around various IDE issues when debugging, etc.

__init.py exposes the settings to the outside world using

from .config import settings
__all__ = ['settings']

and run_me.py has

import my_pkg
print(my_pkg.settings.TEST_VALUE)

and the settings.toml file is

[default]
test_value=5

But when I run run_me.py it throws an error saying

AttributeError: 'Settings' object has no attribute 'TEST_VALUE'

When running/debugging (PyCharm) I have the working directory set to the full path to the top level my_pkg directory, as recommended in various other posts here. The full script path that is being run under the IDE is

"C:\Users\me\Documents\blah\mypkg\mypkg\scripts\run_me.py"

Previously I was using the older method of accessing settings using (at the top of run_me.py)

from dynaconf import settings
settings.load_file(Path(__file__).parent.parent / "settings.toml")

Now I'm trying to convert to the newer, recommend way of configuring dynaconf. I'm clearly missing some nuance. Any tips would be appreciated.

Thanks!

[tjnd89]

I can see in the debugger that

mypkg.settings._loaded_by_loaders = {'toml': {'DEFAULT': <Box: {'test_value': 5}>}}

so it appears that it is loading the file. But I can't seem to access the settings.

[tjnd89]

More testing, I can access the settings value using this syntax

print(mypkg.settings.DEFAULT.TEST_VALUE)

By explicitly specifying the ENVIRONMENT. I can see that I am using the DEFAULT environment because

my_pkg.settings.DEFAULT_ENV_FOR_DYNACONF = 'DEFAULT'

It's as if the loaded settings aren't getting merged into the overall settings ...

[tjnd89]

Ok, found the answer. According to https://github.com/dynaconf/dynaconf/blob/master/3.x-release-notes.md,

Dynaconf is now envless by default.
Historically Dynaconf worked in a multi layered environments for loading data from files, so you were supposed to have a file like:

[default]
key = 'value'

[production]
key = 'value'
Now starting on 3.0.0 the environments are disabled by default, so the same file can be created as.

key = 'value'
And you can still have the environments but only if you explicit specify it when creating your instance.

To have the previous behavior supporting all environments from the first level of a file.

settings = Dynaconf(
environments=True
)

so if I initialize my settings and add the environments keyword.

settings = Dynaconf(
    envvar_prefix="DYNACONF",
    settings_file="settings.toml",
    root_path=ROOT_PATH,
    environments=True
)

The "old_school" method of specifying the settings in settings.toml works where they were under [default]