Empty .env file throws #125

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Open

bsutton opened this issue Jan 26, 2025 · 0 comments

bsutton commented Jan 26, 2025

If the .env file exists but is empty then DotEnv().load() throws a EmptyEnvFileError.

This seems inconsistent to how a missing .env is treated.

If the .env file is missing then a FileNotFoundError is throw but then it is caught and if isOptional=true then the exception is suppressed.

An empty file with isOptional=true should behave in the same way as missing file.

The use case here is that in a debug environment I need a .env file but in release the .env can be empty.

I can't see any reason why these two cases would be treated differently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment