Could you please tweak up your manifest to contain the license for others to distribute?

Hi,
I am using Pycharm 2019.3.1, the package works great when I start pytest by using right-click on the respective test folder from within Pycharm, all environment variables are found and used. However, if I start pytest from the console, the variables are not found. Am I missing a cli parameter that tells pytest to use pytest-dotenv?

Please add, and include them in the source tarball, so they can be used by rpm to validate the package.

"override" is hardcoded by True. Suggest to add _override = early_config.getini("env_override_existing_values") to make this configurable

def pytest_sessionstart(session):
    config = session.config
    if config.getoption("envfile", default=None) is not None:
        load_dotenv(dotenv_path=config.getoption("envfile"), override=True)

When using pytest to test utilities (CLI) or a mix of API and utility which require setting PYTHONPATH, the current set of affairs is not great:

• because pytest_dotenv updates the envvars inside the running process, it's not taken in account by sys.path
• since 7.0, pytest has added a pythonpath configuration entry but that only updates sys.path, so subprocesses don't take that into account

So if one wants to avoid having to set the envvar externally, one has to hit their head on that wall until they figure that both is necessary.

Having special support for PYTHONPATH was understandably rejected in python-dotenv (theskumar/python-dotenv#36) but I figure pytest-dotenv is a lot more specific, and having a coherent PYTHONPATH & sys.path in test contexts seems a lot more sensible in the context of pytest-ing.

NB: I also opened an issue to see if the Pytest folks would be willing to update the pythonpath feature such that it'd also update the envvar: pytest-dev/pytest#10067

Hey there! I'm using this plugin and I've noticed the following behavior, which is somewhat confusing. If I have my pytest-dotenv config as follows:

env_files =
    .env  <-- defines FOOBAR=5
    .env.test  <-- defines FOOBAR=7

then I end up with FOOBAR=5.
I understand this can be fixed with env_override_existing_values=1, but the docs seem to suggest that this is intended for overriding existing env vars in the current process, rather than env vars in a previously listed file. In my opinion, it would make sense to overwrite values from previously specified env files by default, while leaving env_override_existing_values=1 for deciding whether or not existing env vars in the process should be overwritten.

I'd be happy to open a PR if the proposed behavior makes sense.

If pytest is used pytest-dotenv will only load an environment file from the pytest.ini. If py.test is used then the cli arg --envfile will be used.

pytest --envfile <path to .env> does nothing and will fallback to the config given in pytest.ini

Hi,

It seems this is a problem which has just been fixed by python-dotenv upstream (theskumar/python-dotenv#108 ) . It would be better if a 'usecwd=True' been added to find_dotenv in plugin.py.

Thanks very much

I succeeded with running my test with pytest-dotenv from command line as below quote

============================= test session starts ==============================
platform linux -- Python 3.6.9, pytest-5.2.2, py-1.8.0, pluggy-0.13.0
rootdir: /my/local/path/to/pytest-start, inifile: pytest.ini
plugins: forked-1.1.3, dotenv-0.4.0, xdist-1.30.0
collected 1 item

tests/test_dotenv.py .

============================== 1 passed in 0.01s ===============================

Though when running the test with PyCharm test run mode, the plugin not working.
So my question is how to get PyCharm test run working with pytest-dotenv?

The pytest entry_point used for pytest-dotenv is named "env" and thus does collide with other pytest plugins e.g. pytest-env. Thus only one of these plugins can be installed and used.

I'd suggest using the specific plugin name "dotenv" for the pytest entry_point. This is also suggested in the pytest documentation.

For Django projects using django-dotenv and calling dotenv.read_dotenv() from manage.py, installing this library will break manage.py due to a namespace conflict between django-dotenv and python-dotenv (a dependency that this library will install). I know this isn't a Django-specific library and that it would be outside of scope to try to resolve this issue, but might at least be worth a warning in the README.

It would be nice to be able to pass --env-file or something similar as a CLI option. I switch stuff like databases off .env files and would like to avoid maintaining a 1-to-1 of pytest.ini files and .env files. Avoids pytest-dev.ini -> dev.env, pytest-qa.ini -> qa.env and pytest-prod.ini -> prod.env.

This looks like a great little plug-in that will save me from having to remember to prefix my pytest/tox commands with dotenv-run to load my .env file for testing. Would you be amenable to using .env as the default, so the plugin can be used without additional configuration? It's the default used in python-dotenv itself and seems to be largely the default for most things I've seen using this sort of thing.

Hi, I would like to load different files from different conftest files, is this possible?

Thanks!

Hello

pytest-dotenv is very interesting for loading dotenv for integration tests (ie test that depends on the environment), for example to simulate the test environments in CI.

But this approach shall not be used for unit test that shall mock/stub/patch every dependency to outside, and typically the environment variable shall be simulated by something like monkeypatch.setenv. This is the I in FIRST principles (https://medium.com/@tasdikrahman/f-i-r-s-t-principles-of-testing-1a497acda8d6)

How we can restrict pytest-dotenv to only tests marked as "integration_tests"?