Empty .env file throws

[bsutton]

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.