Strict separation of config from code.

I do not have a .env file in the project folder, but I have one in a folder at the top parent directory outside of project folder. Decouple are reading this file.

/home/user/repository/
    | .env # decouple should not read this file
    | github/
        | projects/
            | myproject /
                | manage.py
                | myproject/
                    | settings.py
                    | urls.py
                    | wsgi.py
                | app1/

In the Unix world settings and application parameters are usually evaluated in the following order:

1. CLI arguments (eg. python -u)
2. Environment variables (eg. PYTHONUNBUFFERED=1)
3. Local settings files (eg. ./project/setup.cfg)
4. User settings files (eg. $HOME/.setup.cfg)
5. System settings files (eg. /etc/setup.cfg)

But python-decouple change this order and use the .env file settings even if we've a envvar with diferent value:

https://github.com/henriquebastos/python-decouple/blob/master/decouple.py#L127-L131

I would like to propose the following (backward incompatible) change for the method above:

    def get(self, key):
        try:
            return os.environ[key]
        except KeyError:
            return self.data[key]

Hello, it seems like decouple does not currently support the variables split on multiple lines

# .env file
FOO="foo
bar"

# python
 from decouple import config

>>> config('FOO')
 '"foo'

Of course for a small example like that I could write `FOO="foo\nbar" but for an RSA key it becomes long. It seems that the issue is that the config reader only checks the lines with the = sign

Being able to set defaults is very good since I can set a local development configuration that does not require any effort from new developers to start working on the project. But Id like to be able to tell that some variables must be set in a production environment.

Here is a solution proposal that does not break the current design:

from decouple import config

DEBUG = config('DEBUG', cast=bool)
THIS_IS_REQUIRED = config('THIS_IS_REQUIRED', default='local-value', required_if=(not DEBUG))
THIS_IS_NOT_REQUIRED = config('THIS_IS_NOT_REQUIRED', default='local-value')

In this example situation, if DEBUG is False and the variable THIS_IS_REQUIRED is not set, UndefinedValueError should be raised.

Fala Henrique, blz cara?! Cara, estou com uma dúvida em relação ao python-decouple e queria ver se você poderia responder. Minha dúvida é a seguinte: Usando o decouple vou ter minhas variáveis setadas no .ini ou .env e o decouple vai acessar esse arquivo e pegar esses valores. Até ai tudo bem, mas esse arquivo não é comitado, certo?! Nesse caso, ele ficaria na minha máquina. Como faz quando um novo dev vai desenvolver? E se eu perder esse arquivo (formatar a máquina, der algum pau sei lá). Pode parecer idiota a pergunta mas é uma pergunta que não consegui sanar. Desde já agradeço. Abraço

I am using decouple with a library I am developing. It works just fine when I am testing it from the development directory. However after I install the library and try to import it from a python process started on a arbitrary directory, it cannot find the settings.ini even if I copy it to the directory I am starting python from.

In such cases, where should the settings.ini be placed? this should be made clear in the documentation.

There's no git tag for the 3.2 and 3.3 releases that happened in November. Can you add/push the git tags?

Also, there's nothing in the CHANGELOG about what changed.

Based on commits, I think the changes are as follows:

python-decouple 3.2:

• fixed typos in documentation
• add editorconfig file
• fix handling for configuration values that end in single or double quotes (#78)
• add support for encoding env files in other encodings (#62) (#64)
• improve csv documentation (#59)

python-decouple 3.3:

• enforce search order in settings files
• switch to using strtobool (#71)

Thank you!

Hi. Similarly to django-configurations, it could be very convenient to be able to specify an environment filename with variables, not just to have .env hard-coded. For example, I could therefore specify a set of vars for different environments, e.g. prod.env, staging.env, and I could switch them using another env variable, e.g.:

DECOUPLE_CONFIGURATION=staging.env python program.py

Hi, first of all, thanks for nice library! It's awesome software 👍 I need to use UTF-8 in .env and want to use python-decouple for this, but I suppose it won't work with UTF-8, because it doesn't pass encoding param to open function: https://github.com/henriquebastos/python-decouple/blob/24cc51c7880b79d81b5a75c2d441a41428792aa6/decouple.py#L125 So it will fallback to locale.getpreferredencoding(), as specified in Python docs, which is platform dependent. On my Windows 10 its cp1251, but I want to write UTF-8 in .env and be sure it will be read correctly by python-decouple. It would be nice, if we could pass encoding kwarg to config() and it will be used in open() (or default if this kwarg is not specified) Feel free to notify me, if I can help with something

Using decouple with a Django project to separate passwords from my settings.py file. I've got an element in a .env file, i.e: SECRET_KEY=myrandompassword124$%=

Which returns: raise UndefinedValueError('{} not found. Declare it as envvar or define a default value.'.format(option)) decouple.UndefinedValueError: SECRET_KEY not found. Declare it as envvar or define a default value.

I'm guessing the equals sign at the end of the string is throwing decouple for a loop. Any ideas on how to fix? I'd prefer not to have to change the Django key.

The Csv parsing uses shlex and it usually escape # beacuse it is a comment char. Also it don't support UTF-8 chars.

@henriquebastos Do you think it's better to keep this way or change it?

The shlex splitter hangs with None as input, so config("FOO", default=None, cast=Csv()) hangs the application.

I expected it to return an empty list. I think Csv()(None) should return [] because if it was a required config, it would fail before.

from decouple import Csv
Csv()(None)  # it hangs

To understand what was hanging, I tried it:

from shlex import shlex
splitter = shlex(None, posix=True)
list(splitter)  # it hangs

Based on docs:

Since the split() function instantiates a shlex instance, passing None for s will read the string to split from standard input.)

Hi,

Thank you so much for this great package.

Would it be possible to do a fallback on .env.example when the value is not in .env?

Currently, in our github action, we have to rename .env.example to .env in order to run the tests. Also, when someone adds a value to .env.example that I don't really need, I should still be able to run the application. This will allow .env to be shorter and contains only the values that I need to change.

Pull Request #137 refactored by Sourcery.

Since the original Pull Request was opened as a fork in a contributor's repository, we are unable to create a Pull Request branching from it.

To incorporate these changes, you can either:

1. Merge this Pull Request instead of the original, or

2. Ask your contributor to locally incorporate these commits and push them to the original Pull Request

   Incorporate changes via command line

   git fetch https://github.com/henriquebastos/python-decouple pull/137/head
   git merge --ff-only FETCH_HEAD
   git push

NOTE: As code is pushed to the original Pull Request, Sourcery will re-run and update (force-push) this Pull Request with new refactorings as necessary. If Sourcery finds no refactorings at any point, this Pull Request will be closed automatically.

See our documentation here.

Help us improve this pull request!

Added a method called get() in AutoConfig class. It will basically produce the same results as calling config() object, but more intuitive because get is an action. Therefore instead of just calling config object, we call config's get method: config.get()